Re: Passing '-arch pcc' to gfortran-mp-4.8: unrecognized command line option

2013-11-10 Thread Joshua Root
On 2013-11-10 18:00 , Blair Zajac wrote: > I was thinking that if gfortran doesn't accept -arch for any platform, > then this looks like a ppc bug because nobody else has reported it for > x86_64? Apparently recent FSF GCCs do have limited support for -arch. I think they only allow one arch to be

Re: Passing '-arch pcc' to gfortran-mp-4.8: unrecognized command line option

2013-11-09 Thread Blair Zajac
On 11/09/2013 10:16 PM, Joshua Root wrote: On 2013-11-10 08: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 t

Re: Passing '-arch pcc' to gfortran-mp-4.8: unrecognized command line option

2013-11-09 Thread Joshua Root
On 2013-11-10 08: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

Re: Passing '-arch pcc' to gfortran-mp-4.8: unrecognized command line option

2013-11-09 Thread Ryan Schmidt
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:

Passing '-arch pcc' to gfortran-mp-4.8: unrecognized command line option

2013-11-09 Thread Blair Zajac
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