On Thu, Jun 11, 2009 at 11:58 AM, David Cournapeau<[email protected]> wrote: > Ignore diagnose.py for the time being - what does f2py says ?
running build running config_fc running build_src building extension "ese" sources f2py options: [] adding '/tmp/tmpFE_lPq/src.macosx-10.5-i386-2.5/fortranobject.c' to sources. adding '/tmp/tmpFE_lPq/src.macosx-10.5-i386-2.5' to include_dirs. creating /tmp/tmpFE_lPq creating /tmp/tmpFE_lPq/src.macosx-10.5-i386-2.5 copying /System/Library/Frameworks/Python.framework/Versions/2.5/Extras/lib/python/numpy/f2py/src/fortranobject.c -> /tmp/tmpFE_lPq/src.macosx-10.5-i386-2.5 copying /System/Library/Frameworks/Python.framework/Versions/2.5/Extras/lib/python/numpy/f2py/src/fortranobject.h -> /tmp/tmpFE_lPq/src.macosx-10.5-i386-2.5 running build_ext customize UnixCCompiler customize UnixCCompiler using build_ext customize NAGFCompiler customize AbsoftFCompiler customize IbmFCompiler Could not locate executable g77 Could not locate executable f77 Could not locate executable f95 customize GnuFCompiler customize Gnu95FCompiler Couldn't match compiler version for 'GNU Fortran (GCC) 4.3.3\nCopyright (C) 2008 Free Software Foundation, Inc.\n\nGNU Fortran comes with NO WARRANTY, to the extent permitted by law.\nYou may redistribute copies of GNU Fortran\nunder the terms of the GNU General Public License.\nFor more information about these matters, see the file named COPYING\n' customize G95FCompiler customize G95FCompiler customize G95FCompiler using build_ext Removing build directory /tmp/tmpFE_lPq The odd thing is that I'm running my locally installed copy of F2PY, but it is still using files from the system-wide version (installed in /System) of NumPy. _______________________________________________ Numpy-discussion mailing list [email protected] http://mail.scipy.org/mailman/listinfo/numpy-discussion
