The general problem with libreadline is that a lot of programs outside of Sage use it. So many distributions break if we just LD_LIBRARY_PATH a different version of libreadline, suddenly your shell doesn't work any more etc. There are then hacks for Suse and Arch linux in the readline spkg to perhaps copy the system readline. Then the shell does work but some programs in Sage perhaps no longer. It seems like some of the assumption about the locations of files is the readline spkg-install are violated on your version of Suse.
Really, this is why LD_LIBRARY_PATH is considered a bad solution for forcing libraries that doesn't scale to big projects. This is not a new conclusion, many others have been burned there before. The known solution to this is to use rpaths. This is what the compilerwrapper http://trac.sagemath.org/sage_trac/ticket/10572 is about. -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
