[SciPy-user] forcing Sun's f77 instead of g77?

[Pearu Peterson]

On Tue, 3 Sep 2002, Skip Montanaro wrote:

> 
> Trying to build SciPy on Solaris I get this output when compiling
> special/specfun/specfun.f:
> 
>     [ chunka, chunka, chunka, ... ]
>     /home/skip/src/scipy/special/specfun/specfun.f: In subroutine `stvhv':
>     /home/skip/src/scipy/special/specfun/specfun.f:12602: warning: `pu0' might be used uninitialized in this function
>     /home/skip/src/scipy/special/specfun/specfun.f:12603: warning: `qu0' might be used uninitialized in this function
>     /home/skip/src/scipy/special/specfun/specfun.f:12614: warning: `bf' might be used uninitialized in this function
>     /home/skip/src/scipy/special/specfun/specfun.f:12617: warning: `byv' might be used uninitialized in this function
>     /usr/ccs/bin/as: "/var/tmp/cc9skPsN.s", line 57958: error: constant value must be between -4096 and 4095
> 
> Scrolling back through the output I see that it's compiling with g77 but
> assembling with Sun's assembler.  When I built Python I configured using
> --without-gcc.  Is there anything similar to get the SciPy build to favor
> the vendor Fortran compiler over g77 short of renaming or deleting g77?

Use
  python setup.py build build_flib --fcompiler=<vendor>

where <vendor> can be
      Absoft
      Sun
      SGI
      Intel
      Itanium
      NAG
      Compaq
      Digital
      Gnu
      VAST

Pearu