When I build sage-1.4.1.2 on my x86_64-Linux machine (Red
Hat Enterprise Linux 4 - As edition), I get the following
error during the givaro build:

: /usr/local/gcc-4.1.1/x86_64-Linux/lib/../lib/libstdc++.so: could not read symb
ols: File in wrong format

This is happening because the code is incorrectly trying to use

  /usr/local/gcc-4.1.1/x86_64-Linux/lib/libstdc++.so

when it should be using

  /usr/local/gcc-4.1.1/x86_64-Linux/lib64/libstdc++.so

In other words, my machine is a "multilib" machine - it has
libraries for both 32-bit and 64-bit code.  Unfortunately
the code in givaro is incorrectly trying to use 32-bit
code together with 64-bit code.

I have tracked down that the problem is due to the macro
AC_LIBTOOL_SYS_DYNAMIC_LINKER in aclocal.m4. (aclocal.m4
is used to create configure).  I reported the problem to
the libtool folks and suggested a possible solution.  It
looks like they have incorporated my solution into the
stable branch of libtool (currently libtool-1.5.23a).

Until the givaro developers start to use an updated version
of autotools (autoconf, automake, libtool), here is how
to modify givaro for SAGE.

1. Go to www.gnu.org/software/libtool and download the
latest snapshot of the stable branch of libtool.

2. Replace the macro AC_LIBTOOL_SYS_DYNAMIC_LINKER in
givaro/aclocal.m4 (lines 1190-1776) with the code for
the same macro in libtool.m4.

3. Remove configure

4. Run 'autoconf'.  This will create a new configure that
will use the new macro code.

Kate Minola
University of Maryland, College Park

--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sage-support
URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/
-~----------~----~----~----~------~----~------~--~---

Reply via email to