[Numpy-discussion] Built Lapack, Atlas from source.... now numpy.linalg.eig() hangs at 100% CPU

[Chris Colbert]

aside from a smaller numpy install size, what do i gain from linking against
the .so's vs the static libraries?

Chris

On Sat, Mar 28, 2009 at 6:09 PM, Chris Colbert <sccolbert at gmail.com> wrote:

> what does ldconfig do other than refresh the library path?
>
> i copied the .so's  to /usr/local/atlas/lib and added that path to
> /etc/ld.so.conf.d/scipy.conf and then did ldconfig
>
> this was before building numpy
>
> Chris
>
> 2009/3/28 Charles R Harris <charlesr.harris at gmail.com>
>
>>
>>
>> On Sat, Mar 28, 2009 at 3:34 PM, Charles R Harris <
>> charlesr.harris at gmail.com> wrote:
>>
>>>
>>>
>>> 2009/3/28 Chris Colbert <sccolbert at gmail.com>
>>>
>>>> YES! YES! YES! YES! HAHAHAHA! YES!
>>>>
>>>> using these flags in make.inc to build lapack 1.3.1 worked:
>>>>
>>>> OPTS = O2 -fPIC -m32
>>>> NOPTS = O2 -fPIC -m32
>>>>
>>>> then build atlas as normal and build numpy against the static atlas
>>>> libraries (building against the .so's created by atlas causes a linking
>>>> error in numpy build.log.  Numpy will still work, but who knows what
>>>> function may be broken).
>>>>
>>>> Now, off to build numpy 1.3.0rc1
>>>>
>>>> Thanks for all the help gents!
>>>>
>>>
>>> You might need to run ldconfig to get the dynamic linking working.
>>>
>>
>> Oh, and the *.so libs don't install automagically, I had to explicitly
>> copy them into the library.
>>
>> Chuck
>>
>>
>>
>> _______________________________________________
>> Numpy-discussion mailing list
>> Numpy-discussion at scipy.org
>> http://mail.scipy.org/mailman/listinfo/numpy-discussion
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20090328/8f66011d/attachment.html>