| 1 |
On Wed, 22 Jan 2014 13:52:57 +1300 |
| 2 |
François Bissey <fbissey@××××××××××××.nz> wrote: |
| 3 |
|
| 4 |
> We have yet another instance of someone emerging lapack-reference |
| 5 |
> without |
| 6 |
> a valid blas configuration in |
| 7 |
> https://bugs.gentoo.org/show_bug.cgi?id=498490 |
| 8 |
> (not their original problem). |
| 9 |
> I think we should do something about this in lapack-reference and |
| 10 |
> possibly |
| 11 |
> other ebuilds. |
| 12 |
> In pkg_setup, we could run |
| 13 |
> eselect blas update |
| 14 |
> to make sure that a valid configuration is active |
| 15 |
> and display an informational message about the blas provider |
| 16 |
> used with the output of |
| 17 |
> eselect blas show |
| 18 |
> |
| 19 |
> Who thinks is a good/bad idea? |
| 20 |
> |
| 21 |
> Francois |
| 22 |
> |
| 23 |
|
| 24 |
For one, I'm in favor of something like this - though I probably don't have |
| 25 |
much say in the matter. I've been bitten by not eselecting {blas, cblas, |
| 26 |
lapack} after an upgrade. And I've even posted on this forum the problem. |
| 27 |
|
| 28 |
http://article.gmane.org/gmane.linux.gentoo.science/1915 |
| 29 |
http://article.gmane.org/gmane.linux.gentoo.science/1916 |
| 30 |
|
| 31 |
I resolved things, quite accidently, by re-eselecting the important |
| 32 |
components which were eselected before the upgrade. |
| 33 |
|
| 34 |
Steve |
Archives