On Tue, Oct 13, 2009 at 8:37 AM, Tim Joseph Dumol <t...@timdumol.com> wrote: > The readline problem can be worked around by copying the system version of > libreadline to $SAGE_ROOT$/local/lib/. Well, at least it worked on my > machine.
Thanks. I'm trying rebuilding singular and readline to see what the real cause of the problem is, since I'm curious. William > > On Tue, Oct 13, 2009 at 10:39 PM, Jason Grout <jason-s...@creativetrax.com> > wrote: >> >> William Stein wrote: >> > On Mon, Oct 12, 2009 at 3:04 PM, Jason Grout >> > <jason-s...@creativetrax.com> wrote: >> >> William Stein wrote: >> >>> On Mon, Oct 12, 2009 at 11:22 AM, Jason Grout >> >>> <jason-s...@creativetrax.com> wrote: >> >>>> I have found having the up-to-date alpha/rc on alpha.sagenb.org to be >> >>>> extremely handy for testing to see if a certain patch fixes another >> >>>> bug, >> >>>> testing the effects of patches that have gone in, etc. Right now >> >>>> it's >> >>>> running alpha1, though. Can we make some sort of automated process >> >>>> to >> >>>> update it? Or maybe better, add upgrading alpha.sagenb.org to the >> >>>> list >> >>>> of things to do when releasing an alpha/rc? >> >>>> >> >>>> Thanks! >> >>> I sense you becoming release manager in the near future :-) >> >> >> >> I'd be more than happy to just stick to typing "./sage -upgrade" if I >> >> knew where alpha.sagenb.org was. >> >> >> >> Jason >> > >> > Do "ssh s...@sagenb" from boxen. Then >> > >> > s...@sagenb:~$ cd sage_install/ >> > s...@sagenb:~/sage_install$ ls >> > sage sage-4.1.1 sage-alpha >> > s...@sagenb:~/sage_install$ cd sage-alpha/ >> > s...@sagenb:~/sage_install/sage-alpha$ ls >> > COPYING.txt examples install.log makefile sagenb >> > spkg >> > data foo ipython README.txt sage-python >> > tmp >> > devel HISTORY.txt local sage sage-README-osx.txt >> > s...@sagenb:~/sage_install/sage-alpha$ >> >> >> Okay, I tried upgrading using ./sage -upgrade, and it stopped on an >> error in readline (undefined symbol PC, I think). So now I'm building >> rc0 from scratch. However, it seems like I shouldn't be building sage >> on the "production" virtual machine (and thus using up resources). Is >> there another VM that is set up for doing builds and binary distributions? >> >> Thanks, >> >> Jason >> >> >> >> -- >> Jason Grout >> >> >> > > > > -- > Tim Joseph Dumol <tim (at) timdumol (dot) com> > > > > -- William Stein Associate Professor of Mathematics University of Washington http://wstein.org --~--~---------~--~----~------------~-------~--~----~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---