[Numpy-discussion] atlas not found, why?
David Cournapeau
david at ar.media.kyoto-u.ac.jp
Fri Nov 7 04:49:03 EST 2008
T J wrote:
> On Fri, Nov 7, 2008 at 1:58 AM, T J <tjhnson at gmail.com> wrote:
>
>> That the fortran wrappers were compiled using g77 is also apparent via
>> what is printed out during setup when ATLAS is detected:
>>
>> gcc -pthread _configtest.o -L/usr/lib/atlas -llapack -lblas -o _configtest
>> ATLAS version 3.6.0 built by root on Fri Jan 9 15:57:20 UTC 2004:
>> UNAME : Linux intech67 2.4.20 #1 SMP Fri Jan 10 18:29:51 EST
>> 2003 i686 GNU/Linux
>> INSTFLG :
>> MMDEF : /fix/g/camm/atlas3-3.6.0/CONFIG/ARCHS/P4SSE2/gcc/gemm
>> ARCHDEF : /fix/g/camm/atlas3-3.6.0/CONFIG/ARCHS/P4SSE2/gcc/misc
>> F2CDEFS : -DAdd__ -DStringSunStyle
>> CACHEEDGE: 1048576
>> F77 : /usr/bin/g77, version GNU Fortran (GCC) 3.3.3 20031229
>> (prerelease) (Debian)
>> F77FLAGS : -fomit-frame-pointer -O
>> CC : /usr/bin/gcc, version gcc (GCC) 3.3.3 20031229
>> (prerelease) (Debian)
>> CC FLAGS : -fomit-frame-pointer -O3 -funroll-all-loops
>> MCC : /usr/bin/gcc, version gcc (GCC) 3.3.3 20031229
>> (prerelease) (Debian)
>> MCCFLAGS : -fomit-frame-pointer -O
>> success!
>>
>>
>
> That was intended to be a question.
>
Yes, this output is generated by a call to atlas function ATL_buildinfo,
the exact same I used for the bug report,
David
More information about the NumPy-Discussion
mailing list