Re: [Numpy-discussion] glibc memory corruption when running numpy.test()

2008-11-20 Thread Charles R Harris
On Thu, Nov 20, 2008 at 2:29 AM, David Cournapeau <[EMAIL PROTECTED]>wrote: > On Thu, Nov 20, 2008 at 6:14 PM, Hoyt Koepke <[EMAIL PROTECTED]> wrote: > > > > > I believe the logs I attached (or rather linked to) don't involve > > atlas or lapack or any compiler flags. > > Ah, yes, sorry, I missed

Re: [Numpy-discussion] glibc memory corruption when running numpy.test()

2008-11-20 Thread David Cournapeau
On Thu, Nov 20, 2008 at 6:14 PM, Hoyt Koepke <[EMAIL PROTECTED]> wrote: > > I believe the logs I attached (or rather linked to) don't involve > atlas or lapack or any compiler flags. Ah, yes, sorry, I missed the build.log one. The only thing which surprises me a bit is the size of long double (I

Re: [Numpy-discussion] glibc memory corruption when running numpy.test()

2008-11-20 Thread Hoyt Koepke
Hi, > I honestly don't think those flags matter much in the case of > numpy/scipy. In particular, using SSE and co automatically is simply > impossible in numpy case, since the C code is very generic (non-aligned > - non contiguous items) and the compiler has no way to know at compile > time which

Re: [Numpy-discussion] glibc memory corruption when running numpy.test()

2008-11-20 Thread David Cournapeau
On Thu, 2008-11-20 at 00:26 -0800, Hoyt Koepke wrote: > Hi, > > Sorry; my first message wasn't under 40 KB with the attachments, so > here's the same message but with the log files at > http://www.stat.washington.edu/~hoytak/logs.tar.bz2. > > > > Which ones ? > > Sorry; ATLAS = 3.9.4 and lapack

Re: [Numpy-discussion] glibc memory corruption when running numpy.test()

2008-11-20 Thread Hoyt Koepke
Hi, Sorry; my first message wasn't under 40 KB with the attachments, so here's the same message but with the log files at http://www.stat.washington.edu/~hoytak/logs.tar.bz2. > Which ones ? Sorry; ATLAS = 3.9.4 and lapack=3.2. I'll give 3.8.2 a shot per your advice. > You should not do that,

Re: [Numpy-discussion] glibc memory corruption when running numpy.test()

2008-11-19 Thread David Cournapeau
On Wed, 2008-11-19 at 23:41 -0800, Hoyt Koepke wrote: > Attached. > > I had a bunch of issues getting things to install with lapack and > ATLAS. Which ones ? > In the end I had to specify the following environment > variables (+ appropriate command line options to ATLAS & lapack) to > get it t

Re: [Numpy-discussion] glibc memory corruption when running numpy.test()

2008-11-19 Thread Hoyt Koepke
Sorry; I also added '-fPIC' to the compile flags, though it may work without having it there. I just got errors related to not having it and so threw it at everything... --Hoyt On Wed, Nov 19, 2008 at 11:41 PM, Hoyt Koepke <[EMAIL PROTECTED]> wrote: > Attached. > > I had a bunch of issues get

Re: [Numpy-discussion] glibc memory corruption when running numpy.test()

2008-11-19 Thread Hoyt Koepke
Attached. I had a bunch of issues getting things to install with lapack and ATLAS. In the end I had to specify the following environment variables (+ appropriate command line options to ATLAS & lapack) to get it to work. If there's an easier way, let me know. export FLAGS='-march=core2 -mtune=

Re: [Numpy-discussion] glibc memory corruption when running numpy.test()

2008-11-19 Thread David Cournapeau
On Wed, 2008-11-19 at 23:23 -0800, Hoyt Koepke wrote: > Hello, > > Sorry about this bug report I know how much us programmers like > these kind of bugs :-/. > > In testing the latest svn version of numpy (6083), I get a memory > corruption error: > > test_csingle (test_linalg.TestSolve) ...

[Numpy-discussion] glibc memory corruption when running numpy.test()

2008-11-19 Thread Hoyt Koepke
Hello, Sorry about this bug report I know how much us programmers like these kind of bugs :-/. In testing the latest svn version of numpy (6083), I get a memory corruption error: test_csingle (test_linalg.TestSolve) ... ok test_double (test_linalg.TestSolve) ... ok test_empty (test_linalg.Te