On 03/07/2011 03:55 PM, John Cartwright wrote: > Thanks for your reply Ralf. I'm not sure if it's a warning or error, output > looks like: > > ... > building library "npymath" sources > 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 GnuFCompiler using config > ... > > Not sure about the best way to move g77 off the path since it shares the same > directory as gfortran and would require sysadmin intervention. > > Is there no way through site.cfg or some other means to force the setup.py to > ignore g77? > > --john > > On Mar 7, 2011, at 12:56 AM, Ralf Gommers wrote: > >> On Mon, Mar 7, 2011 at 7:18 AM, John Cartwright >> <john.c.cartwri...@comcast.net> wrote: >>> Hello All, >>> >>> I'm trying to compile 1.5.1 on a RHEL5 system and I'm specifying: >>> >>> python setup.py config_fc --fcompiler=gnu95 build >>> >>> when doing the build. I see the message "Found executable >>> /usr/bin/gfortran" - so far so good. However when I go to install using: >>> >>> python setup.py install >>> >>> I see the warnings "gnu: no Fortran 90 compiler found". How can I avoid >>> this? install doesn't recognize the fcompiler option.
Does either of these work? python setup.py config_fc --fcompiler=gnu95 build install python setup.py config_fc --fcompiler=gnu95 build --fcompiler=gnu95 install The sooner numpy gets rid of distutils the better... Dag Sverre _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
