Re: [Numpy-discussion] atlas not found, why?

2008-11-07 Thread David Cournapeau
David Cournapeau wrote: Ok, I took a brief look at this: I forgot that Ubuntu and Debian added an aditional library suffix to libraries depending on gfortran ABI. I added support for this in numpy.distutils - which was looking for libraries explicitely; could you retry *without* a site.cfg ?

Re: [Numpy-discussion] atlas not found, why?

2008-11-07 Thread David Cournapeau
T J wrote: With r5986, atlas is still only detected if I declare ATLAS: $ ATLAS=/usr/lib python setup.py build versus $ unset ATLAS; python setup.py build It works for me on Intrepid (64 bits). Did you install libatlas3gf-base-dev ? (the names changed in intrepid). cheers, David

Re: [Numpy-discussion] atlas not found, why?

2008-11-07 Thread David Cournapeau
T J wrote: I fear I am overlooking something obvious. No, I mixed up the names, I meant libatlas-base-dev. It looks like I have the important ones: libatlas-base-dev libatlas-headers libatlas-sse2-dev libatlas3gf-base libatlas3gf-sse2 I have only libatlas-headers,

Re: [Numpy-discussion] atlas not found, why?

2008-11-07 Thread David Cournapeau
On Fri, Nov 7, 2008 at 8:10 PM, T J [EMAIL PROTECTED] wrote: On Fri, Nov 7, 2008 at 2:16 AM, David Cournapeau [EMAIL PROTECTED] wrote: And you have no site.cfg at all ? Wow. I was too focused on the current directory and didn't realize I had an old site.cfg in ~/. Two points: 1) Others

Re: [Numpy-discussion] atlas not found, why?

2008-11-07 Thread T J
On Fri, Nov 7, 2008 at 2:16 AM, David Cournapeau [EMAIL PROTECTED] wrote: And you have no site.cfg at all ? Wow. I was too focused on the current directory and didn't realize I had an old site.cfg in ~/. Two points: 1) Others (myself included) might catch such silliness sooner if the

Re: [Numpy-discussion] atlas not found, why?

2008-11-07 Thread T J
On Fri, Nov 7, 2008 at 1:58 AM, T J [EMAIL PROTECTED] wrote: That the fortran wrappers were compiled using g77 is also apparent via what is printed out during setup when ATLAS is detected: gcc -pthread _configtest.o -L/usr/lib/atlas -llapack -lblas -o _configtest ATLAS version 3.6.0 built by

Re: [Numpy-discussion] atlas not found, why?

2008-11-07 Thread T J
On Fri, Nov 7, 2008 at 1:48 AM, David Cournapeau [EMAIL PROTECTED] wrote: It works for me on Intrepid (64 bits). Did you install libatlas3gf-base-dev ? (the names changed in intrepid). I fear I am overlooking something obvious. $ sudo aptitude search libatlas p libatlas-3dnow-dev

Re: [Numpy-discussion] atlas not found, why?

2008-11-07 Thread T J
On Fri, Nov 7, 2008 at 1:26 AM, David Cournapeau [EMAIL PROTECTED] wrote: David Cournapeau wrote: Ok, I took a brief look at this: I forgot that Ubuntu and Debian added an aditional library suffix to libraries depending on gfortran ABI. I added support for this in numpy.distutils - which was

Re: [Numpy-discussion] atlas not found, why?

2008-11-07 Thread David Cournapeau
T J wrote: On Fri, Nov 7, 2008 at 1:58 AM, T J [EMAIL PROTECTED] wrote: That the fortran wrappers were compiled using g77 is also apparent via what is printed out during setup when ATLAS is detected: gcc -pthread _configtest.o -L/usr/lib/atlas -llapack -lblas -o _configtest ATLAS version

Re: [Numpy-discussion] atlas not found, why?

2008-11-06 Thread David Cournapeau
On Tue, Nov 4, 2008 at 7:59 AM, T J [EMAIL PROTECTED] wrote: 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. Ok, I took a brief look at this: I forgot that Ubuntu and Debian added an

Re: [Numpy-discussion] atlas not found, why?

2008-11-04 Thread Scott Sinclair
T J [EMAIL PROTECTED] 11/04/08 12:59 AM On Mon, Nov 3, 2008 at 10:46 AM, T J [EMAIL PROTECTED] 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

Re: [Numpy-discussion] atlas not found, why?

2008-11-03 Thread T J
On Mon, Nov 3, 2008 at 10:46 AM, T J [EMAIL PROTECTED] 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