A follow-up on this, since it just happened to me again (clearly my memory is not very good).
Deleteing or renaming the original build does not solve it, not does rebuilding the sage library (sage -ba). The shared library files in local/lib (the ones ending in .so) all link back to dependent libraries in the original location, and sage will not run unless these are readable. A quick fix is to make all files in the original build tree world-readable, but that is clearly not a good solution since if that original build gets moved or renamed then the copy will stop working. I thought it would work to go into local/lib (in the copy) and do "LD_LIBRARY_PATH=. ldconfig -n ." but that made no difference. Unless there are new ideas the advice remains: build sage where you want it to be installed; if you do move the build, copy it and make sure that the original remains in place and that the files in it are readable by whoever wants to run the moved (copied) version. John On 17 May 2013 09:00, John Cremona <[email protected]> wrote: > As "that someone" who had this problem: I rebuilt Sage in the place > from which it was to be run. You can change all the file ownerships > and permissions after moving a build, but some of the code was still > linking back to the original build site. In my case the only reason > that did not work was because the original build was not > world-readable, but clearly I wanted the system-installed build not to > rely on anything in a separate place (my home directory). > > Hence my advice for anyone building Sage for use in a system-wide > install is: build it where you want to to be installed. > > John > > On 17 May 2013 00:39, leif <[email protected]> wrote: >> [email protected] wrote: >>> >>> Freshly-installed version of Sage 5.9. >>> First time starting it up, I get the appended. >>> >>> Thoughts? >> >> >> Smells like what recently happened to someone who >> >> - did build Sage as a different user than that trying to run Sage >> - *copied* the Sage installation afterwards (for system-wide installation) >> - did not delete, nor rename the original build directory. >> >> >> (I assume you *did* run 'chown -R ...' and 'chmod -R +rX ...' on >> /usr/share/sage-5.9/, and also ran /usr/share/sage-5.9/sage once as the >> owner [with write permission on the installation tree], to "fix various >> hardcoded paths".) >> >> >> Unfortunately we couldn't exactly track down what (initially) caused the >> problem for him, but I suspect renaming (or removing) the original build >> directory solves the issue. (Some RPATHs might still refer to the original >> installation, with limited/insufficient permissions for other users.) >> >> >> Another cause might be a (probably silently) failed copy command, e.g. via >> NFS, or with wrong options. The safest way to copy a Sage installation is >> to 'tar' and afterwards "untar" it elsewhere (then running 'sage' once to >> update paths); building it "in-place" for a system-wide installation is >> probably better (safer and less error-prone) as well. >> >> Just to make sure: >> >> Does /usr/share/sage-5.9/devel/sagenb/sagenb/misc/sphinxify.py exist? >> >> >> -leif >> >> >> >>> =================================================== >>> ---------------------------------------------------------------------- >>> | Sage Version 5.9, Release Date: 2013-04-30 | >>> | Type "notebook()" for the browser-based notebook interface. | >>> | Type "help()" for help. | >>> ---------------------------------------------------------------------- >>> Traceback (most recent call last): >>> File "/usr/share/sage-5.9/local/bin/sage-ipython", line 6, in <module> >>> from sage.misc.interpreter import SageTerminalApp >>> File >>> >>> "/usr/share/sage-5.9/local/lib/python2.7/site-packages/sage/misc/interpreter.py", >>> line 67, in <module> >>> import os, log, re, new, sys >>> File >>> "/usr/share/sage-5.9/local/lib/python2.7/site-packages/sage/misc/log.py", >>> line >>> 66, in <module> >>> import misc >>> File >>> "/usr/share/sage-5.9/local/lib/python2.7/site-packages/sage/misc/misc.py", >>> line 2082, in <module> >>> import sage.server.support >>> File >>> >>> "/usr/share/sage-5.9/local/lib/python2.7/site-packages/sage/server/support.py", >>> line 19, in <module> >>> import sage.misc.sagedoc as sagedoc >>> File >>> >>> "/usr/share/sage-5.9/local/lib/python2.7/site-packages/sage/misc/sagedoc.py", >>> line 40, in <module> >>> from sagenb.misc.sphinxify import sphinxify >>> ImportError: No module named sagenb.misc.sphinxify >>> Error in atexit._run_exitfuncs: >>> Traceback (most recent call last): >>> File "/usr/share/sage-5.9/local/lib/python/atexit.py", line 24, in >>> _run_exitfuncs >>> func(*targs, **kargs) >>> File >>> >>> "/usr/share/sage-5.9/local/lib/python2.7/site-packages/sage/misc/temporary_file.py", >>> line 51, in delete_tmpfiles >>> from sage.misc.misc import SAGE_TMP >>> File >>> "/usr/share/sage-5.9/local/lib/python2.7/site-packages/sage/misc/misc.py", >>> line 2082, in <module> >>> import sage.server.support >>> File >>> >>> "/usr/share/sage-5.9/local/lib/python2.7/site-packages/sage/server/support.py", >>> line 19, in <module> >>> import sage.misc.sagedoc as sagedoc >>> File >>> >>> "/usr/share/sage-5.9/local/lib/python2.7/site-packages/sage/misc/sagedoc.py", >>> line 40, in <module> >>> from sagenb.misc.sphinxify import sphinxify >>> ImportError: No module named sagenb.misc.sphinxify >>> Error in sys.exitfunc: >>> Traceback (most recent call last): >>> File "/usr/share/sage-5.9/local/lib/python/atexit.py", line 24, in >>> _run_exitfuncs >>> func(*targs, **kargs) >>> File >>> >>> "/usr/share/sage-5.9/local/lib/python2.7/site-packages/sage/misc/temporary_file.py", >>> line 51, in delete_tmpfiles >>> from sage.misc.misc import SAGE_TMP >>> File >>> "/usr/share/sage-5.9/local/lib/python2.7/site-packages/sage/misc/misc.py", >>> line 2082, in <module> >>> import sage.server.support >>> File >>> >>> "/usr/share/sage-5.9/local/lib/python2.7/site-packages/sage/server/support.py", >>> line 19, in <module> >>> import sage.misc.sagedoc as sagedoc >>> File >>> >>> "/usr/share/sage-5.9/local/lib/python2.7/site-packages/sage/misc/sagedoc.py", >>> line 40, in <module> >>> from sagenb.misc.sphinxify import sphinxify >>> ImportError: No module named sagenb.misc.sphinxify >> >> >> -- >> () The ASCII Ribbon Campaign >> /\ Help Cure HTML E-Mail >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "sage-support" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at http://groups.google.com/group/sage-support?hl=en. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/groups/opt_out.
