[Numpy-discussion] f2py_options in setup.py

Fernando Perez fperez.net@gmail....
Fri Jul 18 16:36:25 CDT 2008


Howdy,

setup.py files with calls like

                    f2py_options = ['--fcompiler=gfortran'],

...

when building the extension object used to work.  But now I'm  trying
the same thing with some f90 code and when running the build, it
doesn't seem to go through to f2py:

maqroll[felipe_fortran]> ./setup.py build
running build
running scons
customize UnixCCompiler
Found executable /usr/bin/gcc
customize GnuFCompiler
Found executable /usr/bin/g77
gnu: no Fortran 90 compiler found
gnu: no Fortran 90 compiler found
customize GnuFCompiler
gnu: no Fortran 90 compiler found
gnu: no Fortran 90 compiler found
customize UnixCCompiler
customize UnixCCompiler using scons
Found executable /usr/bin/g++

etc...

If I run f2py itself at the command line, I can give it the compiler
flag correctly.  But via setup.py it  just doesn't seem to be working,
and  I'm at a loss as to what I'm doing wrong.

Any help would be much appreciated.

Cheers,


f

ps - is there an updated f2py guide on the scipy site somewhere?  The
guide I found was the old one from

http://cens.ioc.ee/projects/f2py2e/

But I don't know if, after all  the recent integration with numpy,
all of it remains valid.  It would be good to have f2py documented as
part of numpy, since it's now part of it.


More information about the Numpy-discussion mailing list