Opened 13 years ago
Closed 11 years ago
#34002 closed defect (fixed)
octave-gsl @1.0.8 is using gcc46 and shouldn't be
| Reported by: | liampg72@… | Owned by: | macports-tickets@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.0.4 |
| Keywords: | Cc: | michaelld (Michael Dickens) | |
| Port: | octave-gsl |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
octave-gsl fails at the configure stage due to "-arch i386" flags being passed to g++-mp-4.6.
:info:configure g++-mp-4.6: error: i386: No such file or directory :info:configure g++-mp-4.6: error: unrecognized option '-arch'
I have tried lot's of things to remove these flags but I don't think I'm experienced enough in writing Portfiles to solve this problem... Can anybody help please?
Cheers,
Liam
Attachments (2)
Change History (5)
Changed 13 years ago by liampg72@…
| Attachment: | octave-gsl-debug.txt added |
|---|
comment:1 follow-up: 2 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
| Description: | modified (diff) |
|---|---|
| Summary: | octave-gsl @1.0.8 configure error "-arch i386" need to be removed → octave-gsl @1.0.8 is using gcc46 and shouldn't be |
Please remember to use WikiFormatting.
The octave-gsl portfile makes no mention of gcc46; why is that compiler being used? Is octave-gsl perhaps inheriting the compiler from the gsl port?
Indeed, the log shows "Using compiler 'Mac OS X gcc 4.0'". That's why MacPorts is adding the -arch flags: because it believes it's going to be using a compiler that supports them. The problem that needs to be fixed is that octave-gsl is using gcc46 at all, not that -arch flags are being passed to it.
comment:2 Changed 13 years ago by liampg72@…
Replying to ryandesign@…:
Please remember to use WikiFormatting.
The octave-gsl portfile makes no mention of gcc46; why is that compiler being used? Is octave-gsl perhaps inheriting the compiler from the gsl port?
Indeed, the log shows "Using compiler 'Mac OS X gcc 4.0'". That's why MacPorts is adding the -arch flags: because it believes it's going to be using a compiler that supports them. The problem that needs to be fixed is that octave-gsl is using gcc46 at all, not that -arch flags are being passed to it.
During the configure step, mkoctfile (built by the octave-devel port) is called to get the CC, CXX, etc flags from the octave installation. As octave-devel was built with +gcc46 (CXX=g++-mp-4.6), this is what is returned. It's here in the configure stage that it complains. octave-gsl basically inherits the compiler from the octave(-devel) port, and that uses gcc46!
comment:3 Changed 11 years ago by michaelld (Michael Dickens)
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
debug output