Hmm. The linker is probably already looking there. Maybe the numpy tarball 
included 32-bit binaries. In that case, the linker wouldn't be able to 
link against the 64-bit blas and lapack. Pure conjecture on my part as 
it's been a while since I installed numpy and scipy myself. But I think 
it's a relatively common problem on 64-bit systems: if you're trying to 
link against a library that you're sure is there but the linker says it 
can't find it, often the installed libraries don't match the architecture 
you're trying to link against.

-Jan

On Tue, 21 Aug 2007, Mark Stodola wrote:

> Date: Tue, 21 Aug 2007 08:48:07 -0500
> From: Mark Stodola <[log in to unmask]>
> To: Michael Hannon <[log in to unmask]>
> Cc: Scientific Linux Users mailing list <[log in to unmask]>
> Subject: Re: numpy, scipy on SL5?
> 
> Michael Hannon wrote:
>> Hi, folks.  I'm trying to get numpy and scipy installed on a 64-bit, SL5
>> system.  I installed numpy from the tar ball, and that seemed to go OK,
>> but when I tried to install scipy, there was a complaint, evidently from
>> numpy, that blas and lapack could not be found.  I've installed all of
>> the blas, blas-devel, lapack, and lapack-devel packages.  I guess the
>> problem is to make numpy and scipy look in /usr/lib64, but I haven't
>> figured out how to do that yet.
>> 
>> If you have suggestions, please pass 'em along to me.
>> 
>> Thanks.
>> 
>> 					- Mike
>
> Mike,
>
> Add /usr/lib64 to /etc/ld.so.conf (order matters here if it is an issue, I 
> think).
> Then run 'ldconfig' to update the cache.  See if that helps at all.
>
> Cheers,
> Mark
>
>