Scientific linux is based off Redhat enterprise. Fedora is generally newer and more cutting edge. New libraries get tested in Fedora and then make their way to RHEL/SL. In your case, your glibc is too old for the binaries you are using. And we don't have SL/RHEL binaries as far as I know. Your easiest recourse is to compile Sage from source. It is easy and fun, give it a try!
On Wednesday, April 11, 2012 7:32:09 PM UTC+1, rvau...@gmail.com wrote: > > Benjamin: > > Thanks for the suggestion. Here's what happened. > > As root, I moved /root/.sage /root/.sage_save_0411. > > Then I ran "./sage" from the 4.8 directory and got: > ---------------------------------------------------------------------- > | Sage Version 4.8, Release Date: 2012-01-20 | > | Type notebook() for the GUI, and license() for information. | > ---------------------------------------------------------------------- > python: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by > /root/sage > /sage-4.8-linux-64bit-fedora_release_16_verne_-x86_64-Linux/local/lib/libpython2 > > .6.so.1.0) > > So it got past the libcsage problem, but now it's complaining > about GLIBC_2.14. > > -- To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to sage-support+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
