On 8/18/06, Joris De Ridder <[EMAIL PROTECTED]> wrote:
Sorry about my ignorance about these things. But is lapack_lite linkedto numpy even if you specify the full lapack library?As I understand it, lapack_lite is built and used by numpy as a shared library with a subset of the LAPACK routines.
Afte
Hi,
[PL]: s_wsfe is not LAPACK's routine it's a routine from the g2c library.
[PL]: You have to link it in in addition to lapack_lite.
Thanks for the pointer.
Sorry about my ignorance about these things. But is lapack_lite linked
to numpy even if you specify the full lapack library?
Afte
s_wsfe is not LAPACK's routine it's a routine from the g2c library.
You have to link it in in addition to lapack_lite.
Piotr
On Friday 18 August 2006 18:07, [EMAIL PROTECTED] wrote:
> Hi,
>
> I am correctly assuming that numpy needs the full lapack
> distribution, and not just the few lapack rout
Hi,
I am correctly assuming that numpy needs the full lapack distribution,
and not just the few lapack routines given by atlas? After installing
numpy I still get the warning
ImportError:
/software/python-2.4.1/lib/python2.4/site-packages/numpy/linalg/lapack_lite.so:
undefined symbol: s_wsfe
w
Hi,
In the README.txt of the numpy installation it says that one could use a
site.cfg file to
specify non-standard locations of ATLAS en LAPACK libraries, but it doesn't
explain how.
I have a directory software/atlas3.6.0/lib/Linux_PPROSSE2/ which contains
libcombinedlapack.a libatlas.a
