I successfully compiled and installed app-sci/atlas-blas-3.6.0 (alias dev-libs/atlas-3.6.0) and app-sci/blas-config-1.0.0 on amd64, request to add amd64 keyword to these ebuilds. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Not really! I use a 32-bit install, and that one doesn't compile because the xconfig script defaults to 64-bit libraries. I didn't manage to change the "answer" file that's redirected to the make command so that the ebuild compiles.(In the end I removed the answer file and answered the faulty question correctly by hand, and then it compiled.) It's the fourth question that gives the problem.
Claes: You stated you have a 32bit install. Why do tell us not flag this ebuild ~amd64 if you are not on that architecure ? (32bit on amd64 counts as x86!) Nevertheless: This ebuild is already marked ~amd64, but has serious problems ! See BUG #48823.
Bug #48823 refers to dev-libs/atlas-3.6.0, while I was commenting on app-sci/atlas-blas-3.6.0. These two ebuilds are not quite the same. It looks like dev-libs/atlas-3.6.0 will be deprecated (also see bug #30453).
There is no app-sci/atlas-blas, only app-sci/blas-atlas ! app-sci/blas-atlas-* are hardmasked (package.mask) and they _don't_ work on amd64. There are many shared libraries that link against *-atlas-* libs. That won't work on amd64 when some of the objects aren't compiled with -fPIC. I'll wait until the sci-herd has completed their structural changes before I continue to mark any blas/atlas/lapack dependent app-sci package ~amd64.
I'll close this one, cause the sci herd has managed to get blas-* working, and i already marked blas-atlas and blas- ~amd64. BUT: They will still be in package.mask for some time...
