Re: [Numpy-discussion] Failure to build numpy 1.6.1

2011-11-08 Thread David Cournapeau 
On Tue, Nov 8, 2011 at 9:01 AM, David Cournapeau courn...@gmail.com wrote:
 Hi Mads,

 On Tue, Nov 8, 2011 at 8:40 AM, Mads Ipsen madsip...@gmail.com wrote:
 Hi,

 I am trying to build numpy-1.6.1 with the following gcc compiler specs:

 Reading specs from /usr/lib/gcc/x86_64-redhat-linux/3.4.6/specs
 Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
 --infodir=/usr/share/info --enable-shared --enable-threads=posix
 --disable-checking --with-system-zlib --enable-__cxa_atexit
 --disable-libunwind-exceptions --enable-java-awt=gtk
 --host=x86_64-redhat-linux
 Thread model: posix
 gcc version 3.4.6 20060404 (Red Hat 3.4.6-11)

 I get the following error (any clues at what goes wrong)?

 This looks like a compiler bug (gcc 3.4 is really old). einsum uses
 SSE intrinsics, and old gcc implementations are quite buggy in that
 area.

 Could you try the following, at line 38, to add the following:

 #define EINSUM_USE_SSE1 0
 #define EINSUM_USE_SSE2 0

I meant to add this in the file
numpy/core/src/multiarray/einsum.c.src, and then rebuild numpy

David
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Failure to build numpy 1.6.1

2011-11-08 Thread David Cournapeau 
On Tue, Nov 8, 2011 at 9:20 AM, Mads Ipsen madsip...@gmail.com wrote:

 Yup, that fixes it. For now, we can apply a temporary fix on our build
 system. Is this something that'll go into, say, 1.6.2?

That's more of a workaround than a fix. We need to decide whether we
disable intrinsics altogether or wether we want to drop support for
old compilers.

cheers,

David
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion