From: Marc Vinyals <marcvinyals@velodius.com>
To: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-science] sci-libs/scipy-0.9.0-r1 undefined symbol: clapack_sgesv
Date: Sat, 4 Jun 2011 11:08:46 +0200 [thread overview]
Message-ID: <20110604110846.4e788c2e@pcbox-marc> (raw)
In-Reply-To: <201106041215.18808.fbissey@slingshot.co.nz>
[-- Attachment #1: Type: text/plain, Size: 2041 bytes --]
EL Sat, 4 Jun 2011 12:15:18 +1200
Francois Bissey <fbissey@slingshot.co.nz> escrigué:
> > Here are my logs. You'll find some warnings in the configuration
> > stage, I hope they'll mean something to you. Also, there's no trace
> > of libclapack.so in
> > ldd /usr/lib64/python2.7/site-packages/scipy/linalg/clapack.so.
>
> The output of
> ldd /usr/lib64/python2.7/site-packages/scipy/linalg/clapack.so is
> very suspicious with Atlas it should look like this:
> ldd /usr/lib/python2.7/site-packages/scipy/linalg/clapack.so
> linux-gate.so.1 => (0xb7890000) liblapack.so.0
> => /usr/lib/liblapack.so.0 (0xb732a000) libpython2.7.so.1.0
> => /usr/lib/libpython2.7.so.1.0 (0xb71bb000) libc.so.6
> => /lib/libc.so.6 (0xb7035000) libblas.so.0
> => /usr/lib/blas/atlas/libblas.so.0 (0xb7014000) libcblas.so.0
> => /usr/lib/blas/atlas/libcblas.so.0 (0xb6ff2000) libatlas.so.0
> => /usr/lib/libatlas.so.0 (0xb6933000) libgfortran.so.3
> => /usr/lib/gcc/i686-pc-linux- gnu/4.5.2/libgfortran.so.3 (0xb6871000)
> libm.so.6 => /lib/libm.so.6 (0xb684b000)
> libgcc_s.so.1
> => /usr/lib/gcc/i686-pc-linux-gnu/4.5.2/libgcc_s.so.1 (0xb682d000)
> libpthread.so.0 => /lib/libpthread.so.0 (0xb6813000)
> libdl.so.2 => /lib/libdl.so.2 (0xb680f000)
> libutil.so.1 => /lib/libutil.so.1 (0xb680b000)
> /lib/ld-linux.so.2 (0xb7891000)
>
> So nothing from blas/cblas/lapack was linked into your scipy which is
> very worrying. It may be that there is a problem with your current
> blas&co setup. what's the output of
> ls -la /usr/lib64/libcblas.so
>
> Francois
>
ls -la /usr/lib64/libcblas.so
lrwxrwxrwx 1 root root 26 2 jun 13:44 /usr/lib64/libcblas.so ->
blas/reference/libcblas.so
ls -la /usr/lib64/libblas.so
lrwxrwxrwx 1 root root 25 2 jun 13:43 /usr/lib64/libblas.so ->
blas/reference/libblas.so
ls -la /usr/lib64/liblapack.so
lrwxrwxrwx 1 root root 29 2 jun 13:47 /usr/lib64/liblapack.so ->
lapack/reference/liblapack.so
It looks reasonable to me.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-06-04 9:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-31 13:44 [gentoo-science] sci-libs/scipy-0.9.0-r1 undefined symbol: clapack_sgesv Marc Vinyals
2011-05-31 18:57 ` Francois Bissey
2011-06-01 15:48 ` Marc Vinyals
2011-06-01 19:22 ` Francois Bissey
2011-06-02 10:32 ` Marc Vinyals
2011-06-04 0:15 ` Francois Bissey
2011-06-04 9:08 ` Marc Vinyals [this message]
2011-06-06 19:33 ` Francois Bissey
2011-06-06 21:20 ` Marc Vinyals
-- strict thread matches above, loose matches on Subject: below --
2011-06-07 20:07 Francois Bissey
2011-06-11 4:58 ` Steven Trogdon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110604110846.4e788c2e@pcbox-marc \
--to=marcvinyals@velodius.com \
--cc=gentoo-science@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox