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