On Fri, 27 Feb 2009, mabshoff wrote: > I have a badly hacked together clisp-2.47.spkg for my Sparc Solaris > build, but it does not have all the patches in it that we used for > clisp 2.46. I don't want to spend any more time on this since I have > wasted too much time on clisp instead of doing the ecl switch, but I > would suggest you write up a snippet for a workaround I can stick into > the 3.4 release notes so that we have an "official" solution for this > problem we can point people too. I am just surprised how many build > failures we have gotten from Gentoo users.
Ok Michael, I attached a hopefully detailed and thorough snippet. I will see about the vmware image that you and William would like but I make no promise. I thought there was some generic linux binaries produced. Cheers, Francois --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
Sage currently ship with clisp-2.46. This particular version has a known compilation problem on Gentoo at least on the x86 architecture. If you run into this problem here is a work around to get a fully functional version of sage. Note however that if you complain about a problem in sage to the dev team you should mention that: 1) you use Gentoo, 2) you are using the clisp work around. ----Procedure---- As a work around we will use a version of clisp from portage to build the copy of maxima shipped with sage. These instructions suppose you have started to install sage and run into the error building clisp. 1)So the first step will be to emerge clisp, the stable version at the time of writing is 2.47-r1 (on all archs except sparc) it is suitable. Make sure to emerge clisp with the readline useflag. 2)As the user you use to install sage go into the sage-3.4 folder. We need to create a link for clisp: ln -s /usr/bin/clisp local/bin/clisp.bin Be careful it is really "clisp.bin". 3)Edit the deps file: nano -w spkg/standard/deps and remove (or comment) the two following lines: $(INST)/$(CLISP): $(BASE) $(INST)/$(GMP) $(INST)/$(TERMCAP) $(INST)/$(READLINE) $(SAGE_SPKG) $(CLISP) 2>&1 Next we need to change: $(INST)/$(MAXIMA): $(BASE) $(INST)/$(CLISP) to $(INST)/$(MAXIMA): $(BASE) Save the file. 4)Type "make" and sage compilation should resume starting with maxima. This will enable you get a full working version of sage. However if clisp is still in sage-3.4.1 and you want update using "sage -upgrade" a new deps file will be downloaded and and a compilation of clisp will be attempted again. To avoid this identify the version of clisp in sage-3.4.1 (it currently is clips-2.46.p7 in sage-3.4) and create a dummy file in spkg/installed: touch spkh/installed/clisp-2.46.p7 Question: Why isn't sage moving to clisp-2.47 or later? Sage is moving from clisp altogether. It will replaced by ecl - real soon. The dev team would rather finish the move to ecl than taking the time updating clisp. Any suggestion to update clisp to version 2.47 will be kindly but firmly redirected to /dev/null.