[gpaw-users] Fwd: can't using gpaw-python

Marcin Dulak Marcin.Dulak at fysik.dtu.dk
Wed Oct 23 13:41:05 CEST 2013


On 10/23/2013 01:29 PM, 謝其軒 wrote:
> =================
>
>  python2.7 -c "from numpy.linalg import lapack_lite; print 
> lapack_lite.__file__"
> /home/z955018/Ultimatum/ALLINSTALLATIONS/numpy-1.7.0/lib/python2.7/site-packages/numpy/linalg/lapack_lite.so
>
> ================
>
>  ldd `python2.7 -c "from numpy.linalg import lapack_lite; print 
> lapack_lite.__file__"`
>         linux-vdso.so.1 =>  (0x00007fffa2bfd000)
>         liblapack.so.3 => /usr/lib64/atlas/liblapack.so.3 
> (0x00002b4d40420000)
>         libblas.so.3 => /usr/lib64/atlas/libblas.so.3 (0x00002b4d40b37000)
>         libgfortran.so.1 => /usr/lib64/libgfortran.so.1 
> (0x00002b4d41507000)
>         libm.so.6 => /lib64/libm.so.6 (0x00002b4d4179f000)
>         libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00002b4d41a22000)
>         libc.so.6 => /lib64/libc.so.6 (0x00002b4d41c30000)
>         /lib64/ld-linux-x86-64.so.2 (0x0000003836400000)
>
> ===============
>
> Does it impy numpy has nothing to do with mkl?
>
> and :
>
> ==============
>
>
>  ldd `which gpaw-python` | awk '{print $3}' | xargs -I f sh -c "echo 
> f; ldd f"
>
>
> sh: -c: line 0: syntax error near unexpected token `0x00007fff9a547000'
> sh: -c: line 0: `echo (0x00007fff9a547000); ldd (0x00007fff9a547000)'
> /opt/libxc/lib/libxc.so.1
>         linux-vdso.so.1 =>  (0x00007fffc4dfd000)
>         libgfortran.so.1 => /usr/lib64/libgfortran.so.1 
> (0x00002b5d205df000)
>         libm.so.6 => /lib64/libm.so.6 (0x00002b5d20876000)
>         libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00002b5d20af9000)
>         libc.so.6 => /lib64/libc.so.6 (0x00002b5d20d08000)
>         /lib64/ld-linux-x86-64.so.2 (0x0000003836400000)
> /usr/lib64/atlas/libblas.so.3
>         linux-vdso.so.1 =>  (0x00007fff82282000)
>         libgfortran.so.1 => /usr/lib64/libgfortran.so.1 
> (0x00002b13df9d4000)
>         libc.so.6 => /lib64/libc.so.6 (0x00002b13dfc6b000)
>         libm.so.6 => /lib64/libm.so.6 (0x00002b13dffc2000)
>         /lib64/ld-linux-x86-64.so.2 (0x0000003836400000)
> /usr/lib64/atlas/liblapack.so.3
>         linux-vdso.so.1 =>  (0x00007fff44ffd000)
>         libblas.so.3 => /usr/lib64/atlas/libblas.so.3 (0x00002b9fb4c2f000)
>         libgfortran.so.1 => /usr/lib64/libgfortran.so.1 
> (0x00002b9fb55ff000)
>         libc.so.6 => /lib64/libc.so.6 (0x00002b9fb5896000)
>         libm.so.6 => /lib64/libm.so.6 (0x00002b9fb5bee000)
>         /lib64/ld-linux-x86-64.so.2 (0x0000003836400000)
> /lib64/libpthread.so.0
>         linux-vdso.so.1 =>  (0x00007fffd31fd000)
>         libc.so.6 => /lib64/libc.so.6 (0x0000003836800000)
>         /lib64/ld-linux-x86-64.so.2 (0x0000003836400000)
> /lib64/libdl.so.2
>         linux-vdso.so.1 =>  (0x00007fffe63fd000)
>         libc.so.6 => /lib64/libc.so.6 (0x0000003836800000)
>         /lib64/ld-linux-x86-64.so.2 (0x0000003836400000)
> /lib64/libutil.so.1
>         linux-vdso.so.1 =>  (0x00007fff88b3f000)
>         libc.so.6 => /lib64/libc.so.6 (0x0000003836800000)
>         /lib64/ld-linux-x86-64.so.2 (0x0000003836400000)
> /lib64/libm.so.6
>         linux-vdso.so.1 =>  (0x00007fff131fd000)
>         libc.so.6 => /lib64/libc.so.6 (0x0000003836800000)
>         /lib64/ld-linux-x86-64.so.2 (0x0000003836400000)
> /usr/lib64/librdmacm.so.1
>         linux-vdso.so.1 =>  (0x00007fffa91bd000)
>         libibverbs.so.1 => /usr/lib64/libibverbs.so.1 (0x0000003831e00000)
>         libc.so.6 => /lib64/libc.so.6 (0x0000003836800000)
>         libpthread.so.0 => /lib64/libpthread.so.0 (0x0000003837800000)
>         libdl.so.2 => /lib64/libdl.so.2 (0x0000003837400000)
>         /lib64/ld-linux-x86-64.so.2 (0x0000003836400000)
> /usr/lib64/libibverbs.so.1
>         linux-vdso.so.1 =>  (0x00007fff6c5c1000)
>         libpthread.so.0 => /lib64/libpthread.so.0 (0x0000003837800000)
>         libdl.so.2 => /lib64/libdl.so.2 (0x0000003837400000)
>         libc.so.6 => /lib64/libc.so.6 (0x0000003836800000)
>         /lib64/ld-linux-x86-64.so.2 (0x0000003836400000)
> /opt/torque//lib/libtorque.so.2
>         linux-vdso.so.1 =>  (0x00007fff57bfd000)
>         libc.so.6 => /lib64/libc.so.6 (0x00002b6ba5ff8000)
>         /lib64/ld-linux-x86-64.so.2 (0x0000003836400000)
> /lib64/libnsl.so.1
>         linux-vdso.so.1 =>  (0x00007fffc11fd000)
>         libc.so.6 => /lib64/libc.so.6 (0x0000003836800000)
>         /lib64/ld-linux-x86-64.so.2 (0x0000003836400000)
> /lib64/libgcc_s.so.1
>         linux-vdso.so.1 =>  (0x00007ffffed8a000)
>         libc.so.6 => /lib64/libc.so.6 (0x0000003836800000)
>         /lib64/ld-linux-x86-64.so.2 (0x0000003836400000)
> /lib64/libc.so.6
>         /lib64/ld-linux-x86-64.so.2 (0x0000003836400000)
>         linux-vdso.so.1 =>  (0x00007fff0c3fd000)
> /usr/lib64/libgfortran.so.1
>         linux-vdso.so.1 =>  (0x00007fffae4cb000)
>         libm.so.6 => /lib64/libm.so.6 (0x00002af62fbf1000)
>         libc.so.6 => /lib64/libc.so.6 (0x00002af62fe74000)
>         /lib64/ld-linux-x86-64.so.2 (0x0000003836400000)
>
> ===================
>
>
> it seems that I can't find any mkl stuff in there.
> it's so awkward and....well, there're no clues of mkl?
>
>
no sign of mkl here. Try to run:
strace gpaw-python `which gpaw-test` pw/lfc.py
and watch when mkl is referenced.

Marcin
>
>
> BR,
> chi-hsuan


-- 
***********************************
  
Marcin Dulak
Technical University of Denmark
Department of Physics
Building 307, Room 229
DK-2800 Kongens Lyngby
Denmark
Tel.: (+45) 4525 3157
Fax.: (+45) 4593 2399
email: Marcin.Dulak at fysik.dtu.dk

***********************************

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listserv.fysik.dtu.dk/pipermail/gpaw-users/attachments/20131023/ae1ad5a2/attachment.html>


More information about the gpaw-users mailing list