Michael, you are a genius. For some reason I was setting SAGE_ROOT in my .bashrc on that machine, and it was indeed pointing to a version which no longer exists there. Now it's working and a 64-bit test report will follow.
John On 26 Jan, 11:51, mabshoff <mabsh...@googlemail.com> wrote: > On Jan 26, 3:43 am, John Cremona <john.crem...@gmail.com> wrote: > > Hi John, > > > I just built 3.3.alpha2 ok on a 64-but Suse machine. Instead of using > > the command line "make && ./sage -testall" as I used to do I just did > > "make test". This did not work: after the build finishes this is what > > I see: > > > SAGE build/upgrade complete! > > . local/bin/sage-env && sage-starts && sage-maketest > > Warning: Attempted to overwrite SAGE_ROOT enviroment variable > > local/bin/sage-env: line 251: /home/jec/sage-3.0.4/local/bin/sage- > > check-64: No such file or directory > > make: *** [test] Error 1 > > > I can go back to using the -testall method, but surely "make test" > > should work? Am I doing something wrong? > > Your SAGE_ROOT points to /home/jec/sage-3.0.4 which one has to assume > is wrong when testing 3.3.a2 build from scratch :) > > Maybe some other sage build is picked up on your machine? > > > John > > 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 -~----------~----~----~----~------~----~------~--~---
