On Feb 22, 5:57 am, mabshoff <[email protected]> wrote:
> On Feb 22, 5:49 am, Vincent Delecroix <[email protected]>
> wrote:
<SNIP>
> > libm4ri testsuite failed, please report upstream!
> > sage: An error occurred while installing libm4ri-20090128
>
> We need more context, i.e gzip install.log and please post a link.
The log is at
http://iml.univ-mrs.fr/~delecroi/sage_install_log/install.log.tar.bz2
> This is a Mandriva 2005 box as Vincent told me in IRC and given that
> the current Mandriva releases both fail to compile Python due to gcc
> segfaults I would not be surprised if this is another gcc problem. I
> believe Martin is valgrinding the m4ri test suite, so bugs in there
> seem unlikely [famous last words :)].
And I would not be surprised if the gcc is at fault since it is
somewhat on the old side:
gcc -v
Reading specs from /usr/lib/gcc/i586-mandrake-linux-gnu/3.4.3/specs
Configured with: ../configure --prefix=/usr --libexecdir=/usr/lib --
with-slibdir=/lib --mandir=/usr/share/man --infodir=/usr
/share/info --enable-shared --enable-threads=posix --disable-checking
--enable-long-long --enable-__cxa_atexit --enable-cloc
ale=gnu --disable-libunwind-exceptions --enable-languages=c,c+
+,ada,f77,objc,java --host=i586-mandrake-linux-gnu --with-syst
em-zlib
Thread model: posix
gcc version 3.4.3 (Mandrakelinux 10.2 3.4.3-7mdk)
And I would also not be surprised if aggressive flags like "-mmmx -
msse -msse2 -msse3" in m4ri caused this.
If the compiler really is at fault we need to blacklist it.
Vincent is building gcc 3.4.6 on that box to see if that makes the
problem go away.
Cheers,
Michael
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
