Re: [Numpy-discussion] building 32 bit numpy on 64 bit linux

2013-12-13 Thread David Jones
On 12/13/13 13:48, Julian Taylor wrote: > On 13.12.2013 18:46, David Jones wrote: >> ... >> >> Correction. Of course LD_LIBRARY_PATH isn't seen by the compiler. It >> only applies at run time. How embarrasing:) This isn't the first time >> I've been bitten by that. >> >> I don't mind doing that wi

Re: [Numpy-discussion] building 32 bit numpy on 64 bit linux

2013-12-13 Thread Julian Taylor
On 13.12.2013 18:46, David Jones wrote: > ... > > Correction. Of course LD_LIBRARY_PATH isn't seen by the compiler. It > only applies at run time. How embarrasing:) This isn't the first time > I've been bitten by that. > > I don't mind doing that with manual builds, but what about with pip? Is

Re: [Numpy-discussion] building 32 bit numpy on 64 bit linux

2013-12-13 Thread David Jones
On 12/13/13 11:24, Charles G. Waldman wrote: this might work: CC="gcc -m32" LDSHARED="gcc -m32" FF="gfortran -m32" linux32 python setup.py build > Compiler flags can't be added to CC, they should be in CFLAGS. (and > ld flags go into LDFLAGS). Otherwise you are saying to use

Re: [Numpy-discussion] building 32 bit numpy on 64 bit linux

2013-12-13 Thread David Jones
On 12/13/13 11:24, Charles G. Waldman wrote: this might work: CC="gcc -m32" LDSHARED="gcc -m32" FF="gfortran -m32" linux32 python setup.py build > Compiler flags can't be added to CC, they should be in CFLAGS. (and > ld flags go into LDFLAGS). Otherwise you are saying to use

Re: [Numpy-discussion] building 32 bit numpy on 64 bit linux

2013-12-13 Thread Charles G. Waldman
>>> this might work: >>> >>> CC="gcc -m32" LDSHARED="gcc -m32" FF="gfortran -m32" linux32 python >>> setup.py build Compiler flags can't be added to CC, they should be in CFLAGS. (and ld flags go into LDFLAGS). Otherwise you are saying to use a program called "gcc -m32" (with a space in the name

Re: [Numpy-discussion] building 32 bit numpy on 64 bit linux

2013-12-13 Thread David Jones
On 12/12/13 16:35, Julian Taylor wrote: > On 12.12.2013 20:40, David Jones wrote: >> On 12/12/13 15:54, Julian Taylor wrote: >>> On 12.12.2013 19:58, David Jones wrote: I'm trying to compile 32-bit numpy on a 64 bit Centos 6 system, but fails with the message: "Broken toolchai

Re: [Numpy-discussion] building 32 bit numpy on 64 bit linux

2013-12-13 Thread David Jones
On 12/12/13 16:35, Julian Taylor wrote: > On 12.12.2013 20:40, David Jones wrote: >> On 12/12/13 15:54, Julian Taylor wrote: >>> On 12.12.2013 19:58, David Jones wrote: I'm trying to compile 32-bit numpy on a 64 bit Centos 6 system, but fails with the message: "Broken toolchain

Re: [Numpy-discussion] building 32 bit numpy on 64 bit linux

2013-12-13 Thread David Jones
On 12/12/13 16:35, Julian Taylor wrote: > On 12.12.2013 20:40, David Jones wrote: >> On 12/12/13 15:54, Julian Taylor wrote: >>> On 12.12.2013 19:58, David Jones wrote: I'm trying to compile 32-bit numpy on a 64 bit Centos 6 system, but fails with the message: "Broken toolchai

Re: [Numpy-discussion] repeat array in a fake dim without stride_tricks ?

2013-12-13 Thread Sebastian Berg
Hey, On Thu, 2013-12-12 at 15:20 +0100, Pierre Haessig wrote: > Hello, > > In order to repeat rows or columns of an array as > http://stackoverflow.com/questions/1550130/cloning-row-or-column-vectors > I can use np.repeat as suggested by pv. However, looking at the flags of > the resulting array,

Re: [Numpy-discussion] [SciPy-Dev] ANN: Scipy 0.13.2 release

2013-12-13 Thread David Cournapeau
Hi Ralf, Thanks a lot for the quick fix release. I can confirm it builds and tests correctly on windows, rhel5 and osx (both 32 and 64 bits). cheers, David On Sun, Dec 8, 2013 at 10:06 AM, Ralf Gommers wrote: > Hi, > > I'm happy to announce the availability of the scipy 0.13.2 release. This >