Changing the permissions in the /usr/local/ path so that all users could write seems to have straightened out the build problem. I sudo chmod'ed +w's and then after the build, returned the permissions to 755's.
On Nov 11, 10:30 pm, bill <bill.margo...@gmail.com> wrote: > Howdy all, > > Step 1: I download Sage via metalink: sage-4.6-linux-64bit- > ubuntu_10.04.1_lts-x86_64-Linux.tar.lzma > Step2: Do md5sum. Checks. Move file to my home directory. > Step3: tar --lzma -xvf sage*tar.lzma ;;; seems successful. > Step4: invoke from my work directory: ../sage*/sage > Banner displays: Sage version 4.6 ... > Step 5: continues "The Sage install tree may have moved > (from /scratch/wstein/build/sage-4.6 to /home/bill/sage-4.6- > linux-64...) > Changing various hadcoded paths > (please wait at most a few minutes) > Do not interrupt this. > Done resetting paths ( ;;; many minutes later...) > > _____________________________ > UNhandled SIGBUS: A bus error occurred in Sage. > This probably occurred because a *compiled* component > of Sage has a bug in it (typically accessing invalid memory) > or is not propoerly wrapped with _sig_on, _sig_off. > You might want to run Sage under gdb .... > > Question: what do I do now? (have not debugged with gdm in quite a > while...) > > -sincerely, > Bill. -- 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
