Running the command: $ eselect cblas list shows up empty on my amd64 machine, even though I have atlas installed. I had a poke around, and found the reason. What happens is the following: 1) eselect-cblas uses the file /usr/share/eselect/libs/skel.bash to search for installed implementations. 2) skel.bash considers all library directories from $(get_libdir) which are lib, lib32 and lib64 on my machine. However, it considers only library directories which are *not* symlinks 3) On my machine, /usr/lib64 is a symlink to /usr/lib, therefore lib64 is ignored. 4) When atlas is installed, it installs configuration files into /etc/env.d/cblas/lib64 and /etc/env.d/blas/lib64. However, these aren't scanned, since /usr/lib64 is discarded as being a symlink. My (temporary) solution is to symlink /etc/env.d/cblas/lib to /etc/env.d/cblas/lib64.
I should add that exactly the same problem is apparent for eselect-blas, for the same reasons, and with the analgous temporary fix.
I think you're using an old profile with the lib64 symlink the wrong way around. Could the amd64 team respond to this? "3) On my machine, /usr/lib64 is a symlink to /usr/lib, therefore lib64 is ignored."
(In reply to comment #2) > I think you're using an old profile with the lib64 symlink the wrong way > around. Could the amd64 team respond to this? > > "3) On my machine, /usr/lib64 is a symlink to /usr/lib, therefore lib64 is > ignored." Yes, it's supposed to be /usr/lib -> ../lib64
We don't support that old setup. I'm not sure what migration mechanism exists, although you could move it around by hand if you want.
