Re: [gentoo-science] Testing with GCC 4

[Donnie Berkholz]

Adam Piątyszek wrote:
> One more problem related to the new eselect modules from your overlay. I
> have blas-atlas and lapack-atlas libraries selected using an old
> blas-config and lapack-config mechanism:
>
>   lespaul ~ # blas-config -p
>
>   Current profiles:
>   F77 BLAS: /usr/lib/blas/f77-ATLAS
>   C BLAS: /usr/lib/blas/c-ATLAS
>
>   lespaul ~ # lapack-config -p
>
>   Current profile:
>   F77 LAPACK: /usr/lib/lapack/f77-ATLAS
>
> And after merging your updated eselect modules and *-reference packages, I
> can not switch to them using neither eselect nor blas/lapack-config:
>
>   lespaul ~ # eselect lapack set reference
>   Implementation "reference" already active for libdir "lib"!
>   Failed to switch to implementation "reference" for libdir "lib"!
>   !!! Error: One or more actions have failed!
>   exiting.
>
> Eselect shows that current lapack and blas are the reference ones:
>
>   lespaul ~ # eselect lapack show
>   reference
>
> However, this is not true:
>
>   lespaul ~ # ls -l /usr/lib/liblapack.*
>   lrwxrwxrwx 1 root root 24 maj 28 17:20 /usr/lib/liblapack.a ->
>   lapack/atlas/liblapack.a
>   lrwxrwxrwx 1 root root 25 maj 28 17:20 /usr/lib/liblapack.so ->
>   lapack/atlas/liblapack.so
>   lrwxrwxrwx 1 root root 27 maj 28 17:20 /usr/lib/liblapack.so.0 ->
>   lapack/atlas/liblapack.so.0
>
> Is it a bug?

This problem should only happen when you first use the eselect version,
then switch back to the *-config version, then switch to the eselect
version again. I don't consider it a real bug, because of this.

The deal is that /etc/env.d/lapack/config will specify the
CURRENT="$foo" setting, but it can't know about how things are set up
using *-config rather than the eselect modules.

Thanks,
Donnie