[SciPy-dev] Problem building under Solaris

Pearu Peterson pearu at cens.ioc.ee
Thu Feb 7 04:08:43 CST 2002

On Wed, 6 Feb 2002, Tom Loredo wrote:

> I recently installed Python 2.2 and am trying to install SciPy
> with it.  The machine is a Sun Ultra10 running Solaris (SunOS 5.7).
> The build is crashing when building shared libraries.  The
> problem is that "gcc" is called with a "-lf90" option.  We
> have a Fortran 95 compiler (Sun WorkShop 6 update 1), but it
> doesn't come with a libf90 (it has a few separate libraries).
> In any case, if I just copy the "gcc -shared..." line that
> setup.py spills out before it quits, and delete -lf90 and
> the (null) variables, it appears to link fine.  I cannot
> figure out where "-lf90" gets added to the link command,
> and I don't want to keep building each one by hand as the
> setup script crashes (I've done three so far---I don't know
> how many there would be).  I suspect this is a distutils
> problem, but I thought I'd ask here first for a fix.  I've
> built a lot of Python extensions, and never had this problem
> before.  But I've never built anything requiring F90/95
> compatibility.

The "-lf90" gets added in 
  scipy_distutils/command/build_flib.py: class sun_fortran_compiler

The corresponding
   ver_match =  r'f77: (?P<version>[^\s*,]*)'
seems to catch almost any compiler as a sun_fortran_compiler, and I think
that this can happen too often wrongly.

Tom, you may want to fix sun_fortran_compiler for your compiler and send a

Otherwise, you have always a choice to use gcc fortran compiler as

./setup.py build_flib --fcompiler=g77 build

Currently, scipy contains no F90/F95 programs at all.


More information about the Scipy-dev mailing list