[SciPy-user] Scipy test fails on SUSE 10.0 (gcc 4.0.2) on 64 bit machines

[Marco Leite]

Hi,

Bellow is the output with the increased verbosity level.
All previous tests went ok,  The full log is large but I can send it
if it helps,..

Thank you

Marco.
============================================
Python 2.4.1 (#1, Sep 12 2005, 23:33:18)
[GCC 4.0.2 20050901 (prerelease) (SUSE Linux)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import scipy
>>> scipy.test(10,10)

...(removed - all ok)...

check_y_stride_assert (scipy.linalg.tests.test_fblas.test_zgemv) ... ok
check_y_stride_transpose (scipy.linalg.tests.test_fblas.test_zgemv) ... ok
check_simple (scipy.linalg.tests.test_fblas.test_zscal) ... ok
check_x_bad_size (scipy.linalg.tests.test_fblas.test_zscal)zscal:n=4
 ... ok
check_x_stride (scipy.linalg.tests.test_fblas.test_zscal) ... ok
check_simple (scipy.linalg.tests.test_fblas.test_zswap) ... ok
check_x_and_y_stride (scipy.linalg.tests.test_fblas.test_zswap) ... ok
check_x_bad_size (scipy.linalg.tests.test_fblas.test_zswap)zswap:n=4
 ... ok
check_x_stride (scipy.linalg.tests.test_fblas.test_zswap) ... ok
check_y_bad_size (scipy.linalg.tests.test_fblas.test_zswap)zswap:n=3
 ... ok
check_y_stride (scipy.linalg.tests.test_fblas.test_zswap) ... ok
affine_transform 1 ... FAIL
affine transform 2 ... FAIL
affine transform 3 ... FAIL
affine transform 4 ... FAIL
affine transform 5*** glibc detected *** free(): invalid pointer:
0x0000000000c87740 ***
Aborted



On 3/28/06, Robert Kern <robert.kern at gmail.com> wrote:
>
> Marco Leite wrote:
> > Hello,
> >
> > I've been trying to get scipy to work on 64bit systems, running SUSE
> 10.0
> > with gcc  4.0.2 and g77  3.3.5. The compilation goes ok, but the tests
> > fails (see
> > bellow). The same is happening for two diferent machines (Xeon and
> > Athlon64).
> >
> > I know the doc's say gcc 3.x is recommended, but the same Suse
> > distribution and software  for 32 bits architecture works without any
> > problems (it seems to
> > work well even with the AMD optimized LAPACK library)...
> >
> > Does anybody have any sugestions?
>
> Please try increasing the verbosity and the debug level of the test suite.
> E.g.
>
>   scipy.test(10, 10)
>
> Then the test runner will print out the name of the test before running
> it. That
> we will know which tests are failing or crashing.
>
> --
> Robert Kern
> robert.kern at gmail.com
>
> "I have come to believe that the whole world is an enigma, a harmless
> enigma
> that is made terrible by our own mad attempt to interpret it as though it
> had
> an underlying truth."
>   -- Umberto Eco
>
> _______________________________________________
> SciPy-user mailing list
> SciPy-user at scipy.net
> http://www.scipy.net/mailman/listinfo/scipy-user
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.scipy.org/pipermail/scipy-user/attachments/20060328/f67315da/attachment.html>