From: Francois Bissey <fbissey@slingshot.co.nz>
To: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-science] sci-libs/scipy-0.9.0-r1 undefined symbol: clapack_sgesv
Date: Thu, 2 Jun 2011 07:22:18 +1200 [thread overview]
Message-ID: <201106020722.18860.fbissey@slingshot.co.nz> (raw)
In-Reply-To: <20110601174846.5687d413@pcbox-marc>
> EL Wed, 1 Jun 2011 06:57:03 +1200
>
> Francois Bissey <fbissey@slingshot.co.nz> escrigué:
> > > Hi,
> > >
> > > While updating sage and python to 4.7 and 2.7, I hit a variation of
> > > an old bug (see http://bugs.gentoo.org/195619): scipy compiles with
> > > lapack-reference but is unusable. Running in python
> > >
> > > import scipy.optimize
> > >
> > > fails with
> > >
> > > [...]
> > >
> > > from scipy.linalg import clapack
> > >
> > > ImportError:
> > > /usr/lib64/python2.7/site-packages/scipy/linalg/clapack.so: undefined
> > > symbol: clapack_sgesv
> > >
> > > I tried rebuilding numpy and scipy with lapack provided (eselect) by
> > > lapack-reference, blas provided by blas-reference, cblas provided by
> > > gsl and with/without clapack with the same result.
> > >
> > > Then I tried rebuilding numpy and scipy with lapack, blas and cblas
> > > provided (eselect) by atlas and scipy worked flawlessly.
> > >
> > > Should scipy depend on a specific lapack provider instead of a
> > > virtual? Enable it at compile time? Is it an unfortunate
> > > combination what fails?
> > >
> > > I can provide build logs if you need them.
> >
> > Hi Marc,
> >
> > Just one thing that I can think of on the top of my head. We recently
> > made scipy depend on arpack and superlu. They also have dependencies
> > on blas/lapack if you didn't rebuild them as well they may cause
> > trouble.
> >
> > I had a similar problem recently but eselecting everything properly
> > worked for me. A last piece of info you could provide: are you using
> > the main tree implementation or bicatali's overlay implementation?
> >
> > Francois
>
> Hi Francois,
>
> I tried rebuilding arpack and superlu without luck. Since you mentioned
> that eselect fixed your problems, I also tried installing
> cblas-reference and using it instead of gsl, also without luck.
>
> I'm using the main tree implementation.
>
Hi Marc,
I have been using bicatali's overlay for a bit and I recompiled all the
cblas/lapack stack from sage a few times with different implementations
in the last few days. The only time i had an issue was when the value
eselected was not what I wanted by accident.
I am curious to see your build log for numpy and scipy. Also what does
ldd /usr/lib64/python2.7/site-packages/scipy/linalg/clapack.so
reports?
Francois
next prev parent reply other threads:[~2011-06-01 19:23 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 [this message]
2011-06-02 10:32 ` Marc Vinyals
2011-06-04 0:15 ` Francois Bissey
2011-06-04 9:08 ` Marc Vinyals
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=201106020722.18860.fbissey@slingshot.co.nz \
--to=fbissey@slingshot.co.nz \
--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