Re: [Discuss-gnuradio] gfortran-4.2.1 build 5666.3 for Xcode 4.0.2 on Mac OS X 10.6.7

[Michael Dickens]

2 comments:

1: Apple's GCC variant does not provide a fortran option (at all); maybe it can 
be hacked on, but I don't know of a project that's done that.  You're better 
off getting the vanilla GCC & compiling it with fortran enabled, or go with a 
fortran-specific project instead.

2: IIRC numpy requires fortran for the purpose of putting that name in place 
for 'f2c'-like purposes -- none of the internal numpy code is actually written 
in fortran and the fortran compiler is never invoked during configuration, 
building, or installation of numpy.  It is invoked is you do a "test" or 
"check", but you can safely ignore those errors.  Once upon a time, the 
MacPorts' py27-numpy port fixed the fortran version via a patch to the numpy 
source (maybe it still does) -- you should be able to do a similar trick to 
convince numpy that it doesn't even need fortran, if that's even necessary.  Of 
course, if you really -do- need fortran for some real purpose (e.g., compiling 
a project that's written with fortran code), then you're better off with 
vanilla GCC.