[SciPy-user] installation on Suse8.1 (blas problem)

[baecker at physik.tu-dresden.de]

[...]

> You can try. If removing -m3dnow will fix the test failure, I'll disable
> it in get_opt..

Nope, this did not work.
Just to understand all this correctly:
If the problem sits in the provided blas, does this mean
that this blas spits out wrong numbers ?
  ((wishing myself back to debian ... ;-))


> > > OTOH, my question may be irrelevant since you are using blas library
> > > provided by Suse... you can try to build blas libraries yourself.
> >
> > if I really have to ;-)
>
> IMHO, it would have been the simplest approach ;-), blas is a relatively
> small library.

After the above I am tempted to  agree ;-).
((One reason for not doing so was that I did not know how I should do
that, maybe I have overlooked that in the docs on the installation ...
What I just did is the following:

  export BLAS_SRC=/home/baecker/INSTALL_PYTHON/blas
  in setup_linalg.py:
  blas_info = {} # test building BLAS from sources.

Compilation seems to work, but I did not figure out,
where the resulting blas is and how this is linked
(in particular how it is ensured that this is the right
one and not the system provided one; presently I get the same error
as before).
What am I doing wrong here ?

Sorry for bothering you with all this ...

Arnd