"T J" tjhnson@gmail.com 11/04/08 12:59 AM
On Mon, Nov 3, 2008 at 10:46 AM, T J tjhnson@gmail.com wrote:
Since these are all in the standard locations, I am building without a site.cfg. Here is the beginning info:
Apparently, this is not enough. Only if I also set the ATLAS environment variable am I able to get this working as expected.
So can someone explain why I *must* define ATLAS. I tried a number of variations on site.cfg and could not get numpy to find atlas with any of them.
When I upgraded from Ubuntu 8.04 to 8.10 it broke my Numpy install (mighty irritating). I haven't looked in detail, but It seems as if some of the packages related to ATLAS have been renamed and the post-upgrade "cleanup" removed the development packages as it considered them obsolete.
I made sure that libatlas-base-dev and libatlas-sse2-dev (this machine supports sse2) were installed and was able to rebuild and install Numpy with no problems. I do not have an ATLAS environment variable.
Cheers, Scott Please find our Email Disclaimer here: http://www.ukzn.ac.za/disclaimer/
On Tue, Nov 4, 2008 at 7:12 PM, Scott Sinclair sinclaird@ukzn.ac.za wrote:
When I upgraded from Ubuntu 8.04 to 8.10 it broke my Numpy install (mighty irritating). I haven't looked in detail, but It seems as if some of the packages related to ATLAS have been renamed and the post-upgrade "cleanup" removed the development packages as it considered them obsolete.
Yes, it is because of the g77->gfortran transition. The new atlas loaded by default is the gfortran built-one, which is installed by default if you installed atlas before. As they remove g77 at the same time, if you rebuild it, numpy will pick up gfortran, so it works by rebuilding.
Fortunately, this won't happen again in a foreseeable future. It means no major distribution use g77 for its standard fortran ABI anymore, except RHEL.
cheers,
David
-
David Cournapeau -
Scott Sinclair