Passing '-arch pcc' to gfortran-mp-4.8: unrecognized command line option
Ryan Schmidt
ryandesign at macports.org
Sat Nov 9 13:49:32 PST 2013
On Nov 9, 2013, at 15:27, Blair Zajac wrote:
>
> I noticed my PPC MacPorts version was out of date so updated it to 2.2.1. After this, there was an octave-devel update which failed to compile while the previous version did. Looking at config.log, I'm seeing this:
>
>
> configure:33534: checking how to get verbose linking output from /opt/local/bin/gfortran-mp-4.8
> configure:33544: /opt/local/bin/gfortran-mp-4.8 -c -pipe -Os -m32 conftest.f >&5
> configure:33544: $? = 0
> configure:33562: /opt/local/bin/gfortran-mp-4.8 -o conftest -pipe -Os -m32 -v -arch ppc conftest.f -lm
> Using built-in specs.
> gfortran-mp-4.8: error: unrecognized command line option '-arch'
> Target: ppc-apple-darwin9
> Thread model: posix
> gcc version 4.8.2 (MacPorts gcc48 4.8.2_0)
>
>
> Given that 10.5 and PPC is pretty old, is it possible that the updates to portconfigure.tcl don't handle PPC as it used to?
I'm not aware of any recent changes in base with regard to arch handling. I'd rather blame the portfiles -- perhaps the fortran recipe that's in the wiki and has been much employed. Or perhaps a problem specific to the octave-devel port. Certainly passing arch flags to gfortran is wrong on any platform.
More information about the macports-dev
mailing list