Home | Docs | Forums | Lists | Bugs | Planet | Store | GMN | Get Gentoo!
Not eligible to see or edit group visibility for this bug.
View Bug Activity | Format For Printing | XML | Clone This Bug
/usr/bin/blas-config: line 1: get_libdir: command not found
-(/usr/lib:$)-> blas-config -c ATLAS /usr/bin/blas-config: line 1: get_libdir: command not found /usr/bin/blas-config: line 1: get_libdir: command not found * /usr//libcblas.so -> blas/atlas/libcblas.so * /usr//libcblas.so.0 -> blas/atlas/libcblas.so.0 * /usr//libcblas.a -> blas/atlas/libcblas.a >>> Regenerating /etc/ld.so.cache... * Caching service dependencies... Marking as critical since it causes the libraries to get installed to /usr/
Hi David. Well, this one I cannot reproduce. I suspect this also may have something to do with toolchain. If you have any more of such (linkage) problems on other packages I'd suggest remerging system (emerge -e system) and trying again. Well, you may even run bootstrap, but I think that would be an overkill. If this does not do it, please reopen the bug and post your emerge info. George
George, It's not a linkage problem. It's a problem with get_libdir not working. It is probably trying to symlink to /usr/${get_libdir}/ but it is returning ane empty string, and getting symlinked to /usr I changed the symlinks in /usr and put them into /usr/lib and lapack-atlas worked find on at least one program I tried. It's specifically a problem with blas-config, as it is blas-config which is symlinking the atlas stuff from blas/atlas/... to /usr/lib/, but in my case it is screwing up and putting them into /usr/ I've tried following blas-config to see where the problem is but I can't seem to find it. I know blas-config calls env-update but after that I get lost...
Um, Ok, what version of blas-config do you have installed? If you are on all-stable profile then its probably 1.0.0. Try the 1.0.1, it should play nicely with new toolchain (to which I still think this is related). If this is indeed an old version that gives these problems, then I'll mark 1.0.1 stable. If not, please post emerge info. George
Doh! Sorry I had 1.0.0 installed. I thought I had 1.0.1 installed but I was mixing it up with lapack-config.
marking invalid