Hello group, I thought I might try to get some work done on a few science-related python packages. A reminder of what was at issue:
Numeric, numarray and scipy all have the ability to link to blas,lapack and atlas libraries. By default, numeric and numarray will build against their own internal, and slower, libraries. I had submitted an ebuild for Numeric which, if USE=atlas, modified the install script to link to the libraries provided by lapack-atlas (and its dependency, blas-atlas), and made lapack-atlas a dependency. One of the devs improved upon my initial offering, suggesting that they were no longer using the atlas use flag, and changed the dependency to virtual lapack. Numeric, numarray, and scipy all need atlas specific information during the build, if it is available. How can I get the atlas information into the setup scripts, if it is appropriate to do so? What happens if Numeric is built against lapack-atlas, and then I use lapack-config to switch to MKL? Numeric would still be linked to libatlas.*, is that a problem? Darren -- [email protected] mailing list
