Error Building sage 4.7

171 views
Skip to first unread message

Robert Goss

unread,
May 11, 2011, 6:25:27 PM5/11/11
to sage-...@googlegroups.com
Dear all,

I downloaded the lastest sage (4.7) and attempted to build it the
fails with the following error:

building 'Crypto.PublicKey._fastmath' extension
creating build/temp.linux-i686-2.6
creating build/temp.linux-i686-2.6/src
gcc -Wall -Wstrict-prototypes -I/home/robert/sage-4.7/local/include
-L/home/robert/sage-4.7/local/lib -fPIC -O3 -fomit-frame-pointer
-Isrc/ -I/home/robert/sage-4.7/local/include/python2.6 -c
src/_fastmath.c -o build/temp.linux-i686-2.6/src/_fastmath.o
/usr/lib/gcc/i586-suse-linux/4.5/cc1: symbol lookup error:
/usr/lib/libppl_c.so.4: undefined symbol:
_ZN23Parma_Polyhedra_Library13have_sse_unitE
error: command 'gcc' failed with exit status 1
Error installing PyCrypto... exiting


This build is on opensuse 11.4 running inside virutalbox. The version
of libppl that opensuse comes with is (according to package manager)
11-3.3

I can supply more information if needed. Is there something simple
that I am missing?

Robert

Dima Pasechnik

unread,
May 11, 2011, 11:02:22 PM5/11/11
to sage-devel


On May 12, 6:25 am, Robert Goss <goss.rob...@gmail.com> wrote:
> Dear all,
>
> I downloaded the lastest sage (4.7) and attempted to build it the
> fails with the following error:

what do you mean by "latest 4.7" ?
The latest testing release is 4.7.rc1, and the latest stable is 4.6.2

Robert Goss

unread,
May 12, 2011, 4:51:10 AM5/12/11
to sage-...@googlegroups.com
> what do you mean by "latest 4.7" ?
> The latest testing release is 4.7.rc1, and the latest stable is 4.6.2
>

Ah right I meant 4.7.rc1 by the lastest 4.7. Should have posted to
another group?

Robert

Volker Braun

unread,
May 12, 2011, 5:22:22 AM5/12/11
to sage-...@googlegroups.com
This is (again) caused by overriding the shared library search path LD_LIBRARY_PATH. In this case, the Sage version of ppl is incompatible with the OS version of ppl. Because we are forcefully loading the Sage version, gcc no longer works. We had similar problems with readline before. The only long-term solution is to use RPATH/RUNPATH instead of the LD_LIBRARY_PATH mechanism.

Volker Braun

unread,
May 12, 2011, 5:41:28 AM5/12/11
to sage-...@googlegroups.com
I'm a bit confused as to what Suse is shipping, the latest ppl release is 11.2

As a workaround, you can delete $SAGE_LOCAL/lib/libppl.so.9.0.0 and replace it with a symlink to your system libppl (/usr/lib64/libppl.so or somesuch). Then re-run make.

Volker


Robert Goss

unread,
May 12, 2011, 1:39:46 PM5/12/11
to sage-...@googlegroups.com
Thanks Volker,

>I'm a bit confused as to what Suse is shipping, the latest ppl release is 11.2

Looking a little at the opensuse site it says that the version of
libppl is 11. and the release (of the package?) is 3.3 if this helps?

>As a workaround, you can delete $SAGE_LOCAL/lib/libppl.so.9.0.0 and replace it with a symlink to your system libppl (/usr/lib64/libppl.so or >somesuch). Then re-run make.

Have done this and it now seems to be compiling fine thanks again.

Robert

Andrei Miau

unread,
Sep 28, 2011, 1:06:44 AM9/28/11
to sage-...@googlegroups.com

I confirm that on openSUSE 11.4 32bit edition this compilation bug is present.
It works after workaround.

On openSUSE 11.4 64bit edition it works fine.

Thank you,
Andrei

PS: I'm compiling sage 4.7.1

Reply all
Reply to author
Forward
0 new messages