[SciPy-user] compiler & lapack issues

[Pearu Peterson]

On Sun, 26 May 2002 gvermeul at polycnrs-gre.fr wrote:

> test_svd fails (I commented out almost everything except for this test, but
> impossible the get rid of the zswap:n=3" message). No failure if I also
> comment out test_svd.

I think zswap:n=3 comes from test_fblas.py.

> > > > Also, where can I get Mandrake lapack.src.rpm's to see what they have
> > > > done?
> 
> I will integrate the latest patches in my lapack. Maybe a patch has been
> superseded by another.
> 
> 
> BTW, a small glitch in build_flib.py (it is fairly dead code):
> 
>     def find_lib_directories(self):
>         lib_dir = []
>         match = r'Reading specs from (.*)/specs'
> 
>         # works I think only for unix...
>         exit_status, out_text = run_command('g77 -v')
> 
> I would replace ('g77 -v') with ('%s -v' % self.f77_compiler)

Fixed. I am really not sure but mingw or cygwin may need it. For unices it
is dead indeed.

> Request: I would like to be able to do something like:
> 
> python setup.py build fc-compiler=/usr/local/bin/g77
> 
> or
> 
> python setup.py build --fc-compiler=g77-2.95.3
> 
> Actually, there is less need to tweak the C compiler than the
> Fortran compiler. Would it not be nice to specify a Fortran
> compiler when running Python's configure (--with-fcc=...)?
> Now I have the choice of hardcoding a specific g77 in SciPy's
> distutils scripts or of relying on dynamic links.

We already have what you requested. Use

  python setup.py build build_flib --fcompiler-exec=/path/to/f77

See also

  python setup.py build_flib --help

Pearu