> Can you look into your lib64 directory and tell us which spkgs got
> installed there?
I had a look at install.log:
grep "local/lib64/" install.log | grep "^/usr/bin/install" | cut -d
4 -f 2 | cut -d / -f 2 | cut -d . -f 1 | sort | uniq
gives:
ecl-11
libcord
libfplll
libfreetype
libgc
libgc
On 9 Dez., 12:05, Volker Braun wrote:
> Good observation. I made a trac ticket with the two possible fixes
> athttp://trac.sagemath.org/sage_trac/ticket/12131
>
Thank you.
> Can you look into your lib64 directory and tell us which spkgs got
> installed there?
I'm sorry, I can't. The unsuccessfu
Hi,
I don't think that there still is a problem with readline on Suse.
after a lot of struggling, I managed to build sage 4.7.2 on openSuSE
12.1 (64bit) on my desktop computer and my laptop a few weeks ago.
Also see the thread
https://groups.google.com/group/sage-devel/browse_thread/thread/02e435
Hi,
finally I succeeded in building sage.
Setting LD_LIBRARY_PATH didn't solve all issues as e.g.
the spkg-install in readline-6.1.spkg expects everything in lib
and not in lib64.
The problem is that several packages including readline install files
(.a, .so etc.) in
$SAGE_LOCAL/local/lib64, but
On 21 Nov., 05:50, caretaker82 wrote:
> Hello~
>
> I am trying to build the latest sage on the latest version of openSUSE
> 12.1 (64-bit), and I have come across another libreadline issue that I
> have not been able to solve:
>
> Error: Readline's build claims to have finished, but files that sh
