OK latest version of gentoo notes for 3.4. 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 but your mileage may vary. 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)portage provides an executable called clisp but sage expect clisp.bin so we create a small script in sage-3.4/local/bin: nano -w local/bin/clisp.bin and then put in #!/bin/sh /usr/bin/clisp Save and make the script executable (chmod 0755 local/bin/clisp.bin ) 3)Execute: touch spkh/installed/clisp-2.46.p7 This will fool the building system into believing that clisp-2.46.p7 is installed in sage. 4)Type "make" and sage compilation should resume starting with maxima. This will enable you get a working version of sage. A few feature such as "sage -upgrade" and "sage -bdist" aren't excepted to work so don't complain about them. Question: Why isn't sage moving to clisp-2.47 or later? Answer: Sage is moving from clisp altogether. It will be 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.
