From: Charles R H. <cha...@gm...> - 2006-06-11 04:47:29
|
Hmm, I just tried this and it took so long on my machine (Athlon64, fc5_x86_64), that I ctrl-c'd out of it. Running ldd on lapack_lite.so shows libpthread.so.0 => /lib64/libpthread.so.0 (0x00002aaaaace2000) libc.so.6 => /lib64/libc.so.6 (0x00002aaaaadfa000) /lib64/ld-linux-x86-64.so.2 (0x0000555555554000) So apparently the Atlas library present in /usr/lib64/atlas was not linked in. I built numpy from the svn repository two days ago. I expect JJ's version is linked with atlas 'cause mine sure didn't run in 11 seconds. Chuck On 6/10/06, Robert Kern <rob...@gm...> wrote: > > JJ wrote: > > Any ideas on where to look for a speedup? If the > > problem is that it could not locate the atlas > > ibraries, how might I assure that numpy finds the > > atlas libraries. I can recompile and send along the > > results if it would help. > > Run ldd(1) on the file lapack_lite.so . It should show you what dynamic > libraries it is linked against. > > > PS. I first sent this to the scipy mailing list, but > > it didnt seem to make it there. > > That's okay. This is actually the right place. All of the functions you > used are > numpy functions, not scipy. > > -- > Robert Kern > > "I have come to believe that the whole world is an enigma, a harmless > enigma > that is made terrible by our own mad attempt to interpret it as though it > had > an underlying truth." > -- Umberto Eco > > > > _______________________________________________ > Numpy-discussion mailing list > Num...@li... > https://lists.sourceforge.net/lists/listinfo/numpy-discussion > |