Robert Goss gmail.com> writes:
>
> 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 wor
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
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
--
To post to this group, send an e
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
> 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
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from thi
On May 12, 6:25 am, Robert Goss 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
>
> building 'Crypto.PublicKey._fa
