[MacPorts] #49516: py27-scipy build failure on PowerBookG4 running Leopard 10.5.8; fortran compiler called with bizarre arguments
MacPorts
noreply at macports.org
Thu Oct 29 15:33:03 PDT 2015
#49516: py27-scipy build failure on PowerBookG4 running Leopard 10.5.8; fortran
compiler called with bizarre arguments
-------------------------------------------------+-------------------------
Reporter: zanderpower@… | Owner: macports-
Type: defect | tickets@…
Priority: Normal | Status: new
Component: ports | Milestone:
Keywords: Leopard PPC G4, fortran called | Version: 2.3.4
incorrectly | Port: py-scipy
-------------------------------------------------+-------------------------
While upgrading py27-scipy on a PowerBook G4 (1.67 Ghz) running Leopard
10.5.8, the build calls the fortran compiler from (macports) gcc47 with
completely wrong arguments:
{{{
building 'dfftpack' library
compiling Fortran sources
Fortran f77 compiler: /mp2/local/bin/gfortran-mp-4.7 -Os -fno-second-
underscore -fPIC -O2 -march=x86-64 -DMS_WIN64 -mtune=generic -msse2
Fortran f90 compiler: /mp2/local/bin/gfortran-mp-4.7 -Os -fno-second-
underscore -fPIC -O2 -march=x86-64 -DMS_WIN64 -mtune=generic -msse2
Fortran fix compiler: /mp2/local/bin/gfortran-mp-4.7 -Wall -g -ffixed-form
-fno-second-underscore -Os -fno-second-underscore -fPIC -O2 -march=x86-64
-DMS_WIN64 -mtune=generic -msse2
creating build/temp.macosx-10.5-ppc-2.7
creating build/temp.macosx-10.5-ppc-2.7/scipy
creating build/temp.macosx-10.5-ppc-2.7/scipy/fftpack
creating build/temp.macosx-10.5-ppc-2.7/scipy/fftpack/src
creating build/temp.macosx-10.5-ppc-2.7/scipy/fftpack/src/dfftpack
compile options:
'-I/mp2/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7
/site-packages/numpy/core/include -c'
gfortran-mp-4.7:f77: scipy/fftpack/src/dfftpack/dcosqb.f
gfortran-mp-4.7: error: unrecognized command line option '-march=x86-64'
gfortran-mp-4.7: error: unrecognized argument in option '-mtune=generic'
gfortran-mp-4.7: note: valid arguments to '-mtune=' are: 401 403 405 405fp
440 440fp 464 464fp 476 476fp 505 601 602 603 603e 604 604e 620 630 740
7400 7450 750 801 821 823 8540 8548 860 970 G3 G4 G5 a2 cell common e300c2
e300c3 e500mc e500mc64 ec603e native power power2 power3 power4 power5
power5+ power6 power6x power7 powerpc powerpc64 rios rios1 rios2 rs64 rsc
rsc1 titan
gfortran-mp-4.7: error: unrecognized command line option '-msse2'
gfortran-mp-4.7: error: unrecognized command line option '-march=x86-64'
gfortran-mp-4.7: error: unrecognized argument in option '-mtune=generic'
gfortran-mp-4.7: note: valid arguments to '-mtune=' are: 401 403 405 405fp
440 440fp 464 464fp 476 476fp 505 601 602 603 603e 604 604e 620 630 740
7400 7450 750 801 821 823 8540 8548 860 970 G3 G4 G5 a2 cell common e300c2
e300c3 e500mc e500mc64 ec603e native power power2 power3 power4 power5
power5+ power6 power6x power7 powerpc powerpc64 rios rios1 rios2 rs64 rsc
rsc1 titan
gfortran-mp-4.7: error: unrecognized command line option '-msse2'
error: Command "/mp2/local/bin/gfortran-mp-4.7 -Os -fno-second-underscore
-fPIC -O2 -march=x86-64 -DMS_WIN64 -mtune=generic -msse2
-I/mp2/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7
/site-packages/numpy/core/include -c -c
scipy/fftpack/src/dfftpack/dcosqb.f -o
build/temp.macosx-10.5-ppc-2.7/scipy/fftpack/src/dfftpack/dcosqb.o" failed
with exit status 1
Command failed: cd
"/mp2/local/var/macports/build/_mp2_local_var_macports_sources_rsync.macports
.org_release_tarballs_ports_python_py-scipy/py27-scipy/work/scipy-0.16.1"
&&
/mp2/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7
setup.py --no-user-cfg config_fc --fcompiler gnu95 --f77exec
/mp2/local/bin/gfortran-mp-4.7 --f77flags=' -Os -fno-second-underscore'
--f90exec /mp2/local/bin/gfortran-mp-4.7 --f90flags=' -Os -fno-second-
underscore' config --cc /mp2/local/bin/gcc-mp-4.7 --include-dirs
/mp2/local/include --library-dirs /mp2/local/lib build
Exit code: 1
}}}
The last time I upgraded py27-scipy (as well as py34-scipy) was in August
(for a rev-bump from @0.16.0_0 to @0.16.0_1) which built with no problem.
The last "true" version upgrade was a few days before the rev-bump when
py-scipy went from @0.15.1_0 to @0.16.0_0--again, no problem. I haven't
upgraded gcc47 since the end of May, so I don't believe gcc47 is the
source of the error (unless scipy now requires a more recent gcc).
Any ideas?
--
Ticket URL: <https://trac.macports.org/ticket/49516>
MacPorts <https://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list