On Jan 26, 2008 5:22 PM, Dexter Douglas <[EMAIL PROTECTED]> wrote: > Hello, > > > On Jan 25, 2008 5:39 PM, Ryan Schmidt > > <[EMAIL PROTECTED]> wrote: > > > > > 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? > > > f2py is used to create interfaces that allow Python > code to call Fortran code. It supports many different > Fortran compilers like Absoft, Lahey, IBM, gfortran, > and g95. > > The support file for g95 is included with the f2py > (numpy) package. The support file lists compiler and > linker flags for g95. Some of the flags are wrong. I > know how to update the g95.py file, but I do not > remember how to reconfigure the f2y/numpy package so > that it will recognize my fixes. I am pretty sure it > is a matter of rerunning one of the setup.py files. I > just do not know which one or how. > > It really is a quick fix -- except for setup.py. I > have tried running several of the setup.py scripts, > but I am either running the wrong ones, or I am not > using the right options. > > If anyone knows which setup.py file I am supposed to > run and the correct way to run it, please let me know.
I would imagine you'd have to apply the fix to the source tree and then rerun the install from the beginning. Have you sent the fixes to g95.py upstream? Cheers Adam _______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo/macports-users
