Hi there, On Tue, Dec 15, 2009 at 01:44:50PM +0000, Dr. David Kirkby wrote: > I've noticed on several occasions people reporting issues when Sage includes > a > library which the system has. This causes conflicts with the linker, and can > result in messages which sometimes include: > > "(possible multiple inclusion of the same file)" > > Readline is one such example, but is by no means unique. This has code > specific > to Suse, as Sage's conflicts with the readline in Suse. > > #################Readline code for Suse Linux ############## > # First we check for OpenSUSE 11.1 since bash is linked dynamically with a > # readline that breaks when we build Sage's readline, so we work around this > # for now. > > if [ -f /etc/SuSE-release ]; then > if [ `grep 11.1 /etc/SuSE-release > /dev/null; echo $?` -eq 0 ]; then > echo "OpenSUSE 11.1 detected" > if [ -d /usr/include/readline/ ]; then > ############################################################
A quick remark: There were a report on sage-support of it being also broken for the new openSuSE 11.2 release (released november 11). I was supposed to look at this but in the end-of-the-year rush, I didn't find the time reinstalling my machine. Moreover, since I'm using my machine for 3 different teaching courses, I didn't want to take the risk to break all. I will do it during the vacations... We most probably want to update the test: > if [ `grep 11.1 /etc/SuSE-release > /dev/null; echo $?` -eq 0 ]; then To match release 11.2 as well. Cheers, Florent -- 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
