On Feb 27, 2:30 pm, François Bissey <fbis...@slingshot.co.nz> wrote:
> On Sat, 28 Feb 2009, mabshoff wrote:
<SNIP>
Hi Francois,
> > 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.
Well, let me rephrase my point: If you
touch spkg/installed/clisp-2.46.p7
Sage's dependency system will assume that that clisp.spkg is
installed, so even if the compilation failed at some point you never
need to mess with "deps", i.e. the instructions should read: "If
building clisp on Gentoo fails emerge ...., then do something about
some script and links, etc, do 'touch spkg/installed/clisp-2.46.p7'
and restart the build process with 'make'" - this should be much more
simple than messing with 'deps' since any dumb mistake in that file
will leave you with a broken Sage dependency system where the standard
question would be "Why did you touch that file" :)
> > 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.
Yep, I can live with that.
> > Cheers,
>
> > Michael
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
-~----------~----~----~----~------~----~------~--~---
