On Fri, Nov 11, 2011 at 07:15:27AM +1300, Francois Bissey wrote: > > On Wed, Nov 9, 2011 at 11:00 PM, Dan Drake <dr...@kaist.edu> wrote: > > > On Wed, 09 Nov 2011 at 09:16PM -0500, Daniel Thau wrote: > > > > Yeah, I considered that possibility. The md5sum for both the > > > > > > pre-compiled > > > > > > > version I tried and the source both matched what they were expected > > > > too. > > > > > > > > $ md5sum sage-4.7.2.tar > > > > b3073997e6c7ec00a269f84ff2e54973 sage-4.7.2.tar > > > > > > > > Any other ideas? > > > > > > Okay, this will be harder then. The first weird thing to me is line 45 > > > of your paste: > > > > > > mv: cannot stat `/scratch/sage-4.7.2/devel/sage-main': No such file or > > > directory > > > > > > That seems strange that the directory/symlink was not created. Maybe try > > > re-installing the Sage library with > > > > > > ./sage -f spkg/standard/sage-4.7.2.spkg > > > > > > and see if that works. > > > > > > The only other thing I can think of right now is your version of gcc, > > > which is pretty old. I don't know if that's the problem, though. > > > > > > > > > Dan > > > > > > -- > > > --- Dan Drake > > > ----- http://mathsci.kaist.ac.kr/~drake > > > ------- > > > > If it helps, I found that directory does in fact exist: > > > > ls /scratch/sage-4.7.2/devel/sage-main > > MANIFEST.in README.txt c_lib export module_list.py pull sage-push > > spkg-delauto spkg-install > > PKG-INFO bundle doc install module_list.pyc sage setup.py > > spkg-dist > > > > Running the command you recommended yielded the following: > > > > http://pastebin.com/2Qv8JTrG > > > > Still doesn't look good. I'll see what I can do about getting a newer > > version of gcc on there. > > That's very strange.That's an error you would get if the file sage-sage > is corupted or edited slightly wrong. I got such an error in sage-on-gentoo > when I removed a little bit too much stuff from sage-sage. > Would you have another sage install in your path by any chance? > > Francois > > This email may be confidential and subject to legal privilege, it may > not reflect the views of the University of Canterbury, and it is not > guaranteed to be virus free. If you are not an intended recipient, > please notify the sender immediately and erase all copies of the message > and any attachments. > > Please refer to http://www.canterbury.ac.nz/emaildisclaimer for more > information. > > -- > 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
No, that was the only sage on the system. I haven't been able to track down the problem with compiling quite yet, but I did figure out the problem with running the pre-compiled sage: The error I got was $ sage python: can't open file 'show-all-if-ambiguous': [Errno 2] No such file or directory So naturally I started digging through Sage's source for show-all-if-amiguous. I tried commenting/removing it whenever I found it, but none of it helped. I accidentally searched in my $HOME rather than in Sage's source while trying this and noticed my .bashrc had 'set show-all-if-ambiguous'. Removing that fixed it! This is particularly weird, as I don't use bash - I use zsh. As far as I know that file was sitting idly on disk, and I don't understand why Sage would parse it or if it did why that line would be problematic. Now that I've figured it out I've got the pre-compiled version of sage running fine. This may also be related to the problem with compiling, but I haven't had a chance to test it out yet. Should I file a bug report?
signature.asc
Description: Digital signature
