I've promoted gfortran to be the default compiler on OS X over vendor compilers (to be more compatible with Linux), and made a similar adjustment for the platform detection. I've promoted gfortran over g77 but not vendor compilers on the other 'nixes. I left the Windows compiler options alone.
https://github.com/numpy/numpy/pull/325 A On Wed, Jun 27, 2012 at 10:46 PM, Ralf Gommers <ralf.gomm...@googlemail.com>wrote: > > > On Mon, Jun 18, 2012 at 9:47 AM, Aron Ahmadia <a...@ahmadia.net> wrote: > >> f2py, by default, seems to prefer g77 (no longer maintained, deprecated, >> speedy, doesn't support Fortran 90 or Fortran 95) over gfortran >> (maintained, slower, Fortran 90 and Fortran 95 support). >> >> This causes problems when we try to compile Fortran 90 extensions using >> f2py on platforms where both g77 and gfortran are installed without >> manually switching the compiler's flags. It is a very minor edit to the >> fcompiler/__init__.py file to prefer gfortran over g77 on OS X, and I can >> think of almost no reason not to do so, since the Vectorize framework (OS X >> tuned LAPACK/BLAS) appears to be ABI compatible with gfortran. I am not >> sure what the situation is on the distributions that numpy is trying to >> support, but my feeling is that g77 should not be preferred when gfortran >> is available. >> > > On Windows g77 is still the default. But indeed, on OS X gfortran is the > recommended Fortran compiler. A PR for this would be useful. > > Ralf > > > _______________________________________________ > NumPy-Discussion mailing list > NumPy-Discussion@scipy.org > http://mail.scipy.org/mailman/listinfo/numpy-discussion > >
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
