On Sat, 28 Feb 2009, mabshoff wrote: > On Feb 27, 2:08 am, François Bissey <fbis...@slingshot.co.nz> wrote: > > On Fri, 27 Feb 2009, mabshoff wrote:
> Ok, it is a little longer than I would have thought it would be. Maybe > we you can stick something in the Sage 3.4 release tour wiki page and > we mention the link from the release notes? > > This also is rather bad: > > 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. > > I.e. not all Gentoo releases fail when building clisp, i.e. at least > one person hanging out in IRC has reported to me that Sage 3.3 just > build for him on a 64 bit Gentoo box. And modifying deps is something > that is next to impossible to detect by remote debugging and touching > the right clisp entry in spkg/installed makes the issue go away. Since > we will not do a thing to clisp until the ecl switch it seems like > this should not be necessary and deps ought to be updated on -upgrade > anyway. I realise it is. At the beginning of my text I said "if you run into this problem" and later I added that in any report they have to mention they use the work around. In fact the instructions presume the compilation stopped because of the problem. It would need to be modified to apply ab initio, of course a seasoned user could easily work it out but I would think they'd try the regular way first. I was very careful with my introduction. > > Another thing: > > 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". > > This is also not the way I would do things. Just give people the clisp > wrapper script modified to call clisp from the default location in > Gentoo with an absolute path (if something like that exists, but it > seems to /usr/bin/clisp). I also suspect that -bdist will break this > way you do it if the new system does not have clisp installed, but > since this is a work around fix with finite life expectancy I think we > don't have to be too nit picky about this :) > /usr/bin/clisp is indeed the binary and the rest is in /usr/lib/clisp-2.47/ crafting a script is doable I guess but it probably will break as well. We know that some stuff will not be supposed to work, -bdist will be one of them. May be this can be added, may be remove the stuff about upgrade and say those 2 won't be supported. > Cheers, > > Michael > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
