I may be going mad but: I just built sage-5.0.beta13 on a machine where I had not built sage since 4.7. It went fine, apparently. Without changing directories after the build finished I typed ./sage and was surprised to see the banner for 4.7 appeared.
Looking at the install log I first saw the message "Installing GCC because your 'gcc' is not so recent." which is a little surprising (the machine has gcc-4.3.4 and is Suse linux; it's the front-end to a big cluster). I also saw that LD_LIBRARY_PATH was set (by me in a startup script) to include $HOME/sage-4.7/local/lib . But the paths in the install log have sage-5.0.beta13. I guess I should unset that LD_LIBRARY_PATH and build it again? But is this an indication of some issue which needs to be looked at? John -- 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
