I would like to publicly endorse this. I also had plenty of issues with
blas and lapack - thankfully they all got resolved as soon as I pulled
eselect::science in as a dep for my ebuilds. I am still afraid that
those ebuilds will break and crumble and I won't be able to do a thing
about it as I could not get any information on how the blas/lapack
problems arise and how come eselect solves them. Sorry for being unable
to provide you with a solution, markus.
Cheers.
On Do 12 Sep 2013 00:16:54 CEST, Markus Oehme wrote:
Hi everybody,
every time I touch anything realted to blas and lapack it blows up in my
face. I just did a fresh install on my computer and I'm getting all sorts of
'cannot find blas' and 'cannot find lapack' (hence currently no sage for me
since half it dependencies don't build). Is there some documentation as to
how to sort this mess out?
Even more fun: I'm currently unable to install eselect::science (which is as
I understand it necessary to flee the above mentioned hell), since
eselect-bashcomp requires >=eselect-1.3.8.
I'm even annoyed enough that I think I could devote some time to helping to
make an end to this snafu -- if somebody points out, how. (My first guess
is, that it would reduce the clusterfuck potential if the science overlay
and main tree machinery [eselect::science I'm looking at you], could be
synced again).
Markus
