On Thu, 26 Feb 2009, mabshoff wrote: > On Feb 25, 3:05 am, water <waterloo2...@gmail.com> wrote: > > if I need to wait sage 3.4 ? > > Hi, > > Sage 3.4 won't fix the issue since it needs to be out by friday at the > latest and I will need to work on other things until then. > > I have thought about this some more and it seems strange that the > compiler would complain about this if it were only related to CFAGS & > friends. > > Francois' compile of 2.46 also failed the same way and 2.47 works > again, so this might be a Gentoo specific bug that was fixed. We used > to patch some clisp files for Gentoo, but those were integrated into > clisp a while ago. If someone could look into the Gentoo bugtracker or > the clisp release notes and point me to a single patch that fixes it I > would be willing to merge it into Sage 3.4 even at this stage. > Hi Michael,
I haven't time to look into that before the release date of sage-3.4, but at least with 3.4 he may have binaries. I suggested an _unsupported_ work around - and I made it clear it was - and I mention it here so you know that's how he got a working sage-3.3 (he seems happy right now) in case he has further problems later on. And also for any other gentoo-er who wants a work around. I suggested using clisp-2.47 from gentoo then creating a link $SAGE_LOCAL/bin/clisp.bin to /usr/bin/lisp edit the deps file to remove the mention of clisp and then continue with the normal make process. For info it compiles and pass make test successfully. 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 -~----------~----~----~----~------~----~------~--~---
