On Jan 25, 2008, at 16:15, Dexter Douglas wrote:
Adam Mercer wrote:
On Jan 25, 2008 3:04 PM, Dexter Douglas wrote:
I am having troubles using f2py with g95.
<snip>
Would someone please tell how to reconfigure f2py?
The short answer is that the g95 fortran compiler is not supported on Mac OS X as the appropriate linking flags have not been implemented. I've just committed r33371 which make numpy and scipy depend on gcc42 until g95 linking is implemented in numpy.
The longer answer is that numpy/distutils/fcompiler/g95.py needs to be modified (along the lines of numpy/distutils/fcompiler/gnu.py) so that it knows how to link on Mac OS X. I'm looking into this and hopefully will be able to send a patch upstream.
I have already begun to modify the linking flags in numpy/distutils/fcompiler/g95.py
But when I rerun f2py, it uses the old flags. I assume that I must rerun one of the setup.py files, but I am not sure which one to run or how to run it (setup.py, setup.py install, setup.py build, etc.)
How do I reconfigure f2py so it sees my fixes? I will be happy to work with you fix this problem.
I don't use this software, but I'm curious: if it compiles with the fortran compiler in gcc42, why expend any effort trying to make it work with a different fortran compiler? Why not just say "it requires gcc42" and be done with it?