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

[Chris Colbert]

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!

Chris




On Sat, Mar 28, 2009 at 4:27 PM, Chris Colbert <sccolbert@gmail.com> wrote:

> yeah, I set -b 32 on atlas...
>
> the bogus atlas config was telling me to set OPTS = O -fPIC -m32 and NOPTS
> = O -fPIC -m32, this caused the make process of lapack to hang.
>
> So i set OPTS = O2 -fPIC -m32 and NOPTS = O0 -fPIC -m32.  Which is the same
> as all of my first attempts except for the presence of -m32. so maybe
> specifying bit size here is needed too.
>
> Chris
>
> 2009/3/28 Charles R Harris <charlesr.harris@gmail.com>
>
>>
>>
>> 2009/3/28 Chris Colbert <sccolbert@gmail.com>
>>
>>> i just ran a dummy config on atlas and its giving me different OPTS and
>>> NOOPTS flags than the scipy tutorial. so im gonna try that and report back
>>>
>>
>> I think that I also had to explicitly specify the bit size flag on the
>> ATLAS command line during various builds, -b32/64 or something like that...
>>
>> Chuck
>>
>>
>>
>> _______________________________________________
>> Numpy-discussion mailing list
>> Numpy-discussion@scipy.org
>> http://mail.scipy.org/mailman/listinfo/numpy-discussion
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.scipy.org/pipermail/numpy-discussion/attachments/20090328/8d8aa950/attachment.html