Opened 18 years ago

Closed 18 years ago

Last modified 16 years ago

#10690 closed defect (duplicate)

BUG: py-scipy build fails on intel mac

Reported by: travis.ruth@… Owned by: erickt@…
Priority: Normal Milestone:
Component: ports Version: 1.3.2
Keywords: py-scipy intel Cc:
Port:

Description (last modified by jmpalacios (Juan Manuel Palacios))

py-scipy fails to build on my macbook pro

Welcome to Darwin!
travis-computer:~ travis$ sudo port clean py-scipy
Password:
--->  Cleaning py-scipy
travis-computer:~ travis$ sudo port -v install py-scipy
--->  Fetching py-scipy
--->  Verifying checksum(s) for py-scipy
--->  Checksumming scipy-0.5.1.tar.gz
--->  Extracting py-scipy
--->  Extracting scipy-0.5.1.tar.gz
--->  Configuring py-scipy
--->  Building py-scipy with target build

(*LONG* snip)

building 'dfftpack' library
compiling Fortran sources
Fortran f77 compiler: f95 -fixed -O4 -target=native
Fortran f90 compiler: f95 -O4 -target=native
Fortran fix compiler: f95 -fixed -O4 -target=native
creating build/temp.darwin-8.7.1-i386-2.4
creating build/temp.darwin-8.7.1-i386-2.4/Lib
creating build/temp.darwin-8.7.1-i386-2.4/Lib/fftpack
creating build/temp.darwin-8.7.1-i386-2.4/Lib/fftpack/dfftpack
compile options: '-c'
f95:f77: Lib/fftpack/dfftpack/dcosqb.f
sh: line 1: f95: command not found
sh: line 1: f95: command not found
error: Command "f95 -fixed -O4 -target=native -c -c Lib/fftpack/dfftpack/dcosqb.f -o build/temp.darwin-8.7.1-i386-2.4/Lib/fftpack/dfftpack/dcosqb.o" failed with exit status 127
Error: Target com.apple.build returned: shell command "cd "/opt/local/var/db/dports/build/_opt_local_var_db_dports_sources_rsync.rsync.darwinports.org_dpupdate_dports_python_py-scipy/work/scipy-0.5.1" && CCFLAGS="-I/opt/local/include -L/opt/local/lib" /opt/local/bin/python2.4 setup.py build" returned error 1
Command output: customize UnixCCompiler
customize UnixCCompiler using build_clib
customize NAGFCompiler
customize AbsoftFCompiler
customize IbmFCompiler
Could not locate executable g77
Could not locate executable f77
Could not locate executable gfortran
Could not locate executable f95
customize GnuFCompiler
customize Gnu95FCompiler
customize G95FCompiler
customize GnuFCompiler
customize Gnu95FCompiler
customize NAGFCompiler
customize NAGFCompiler using build_clib
building 'dfftpack' library
compiling Fortran sources
Fortran f77 compiler: f95 -fixed -O4 -target=native
Fortran f90 compiler: f95 -O4 -target=native
Fortran fix compiler: f95 -fixed -O4 -target=native
creating build/temp.darwin-8.7.1-i386-2.4
creating build/temp.darwin-8.7.1-i386-2.4/Lib
creating build/temp.darwin-8.7.1-i386-2.4/Lib/fftpack
creating build/temp.darwin-8.7.1-i386-2.4/Lib/fftpack/dfftpack
compile options: '-c'
f95:f77: Lib/fftpack/dfftpack/dcosqb.f
sh: line 1: f95: command not found
sh: line 1: f95: command not found
error: Command "f95 -fixed -O4 -target=native -c -c Lib/fftpack/dfftpack/dcosqb.f -o build/temp.darwin-8.7.1-i386-2.4/Lib/fftpack/dfftpack/dcosqb.o" failed with exit status 127

Warning: the following items did not execute (for py-scipy): com.apple.activate com.apple.build com.apple.destroot com.apple.archive com.apple.install
Error: Status 1 encountered during processing.

Change History (6)

comment:1 Changed 18 years ago by markd@…

Summary: py-scipy build fails on intel macBUG: py-scipy build fails on intel mac

comment:2 Changed 18 years ago by vincent@…

this seems to be a duplicate of #11048. the comments to the latter contain a suggested fix. this ticket (though older) should probably be marked duplicate and closed.

comment:3 Changed 18 years ago by pipping@…

Milestone: Available Ports

comment:4 Changed 18 years ago by markd@…

Resolution: duplicate
Status: newclosed

Marking as duplicate.= of #11048.

comment:5 Changed 18 years ago by jmpalacios (Juan Manuel Palacios)

Component: baseports
Description: modified (diff)
Milestone: Available PortsPort Bugs
Priority: BlockerExpected
severity: SeriousNormal

To the original poster: excuse me if this sounds blunt, but please don't file tickets with such an unnecessarily long description, it makes it incredibly difficult to work with them! You can make a better effort at reading the output and determining what's failing and where, thus giving us at least an approximation of the real output we need to fix the issue. Thanks!

I'm trimming the long description to what I beleive is really necessary, even though it may be bit unnecessary as the ticket is already closed and marked as a duplicate (the other one also holding a patch to fix the issue). Still, browsing the ticket as it currently stands is a pain! I'm also fixing ticket values while at it (this neither a blocker nor of serious severity).

-jmpp

comment:6 Changed 16 years ago by (none)

Milestone: Port Bugs

Milestone Port Bugs deleted

Note: See TracTickets for help on using tickets.