On Sun, Apr 25, 2010 at 2:07 PM, Gonzalo Tornaria <torna...@math.utexas.edu> wrote: > I'm having an issue with sage relocation, and wonder if this is known or not. > [...] > Moreover, if I move the directory /scratch/tornaria/sage-4.3.3 away, > and restart sage, it works perfectly, and sqlite and freetype are > loaded from my home.
With risk of being a little obnoxious, I did the following experiment: In addition to moving the directory from the scratch build of sage, I also moved away the libsqlite* files in my home install of sage, since I have libsqlite3-0 3.5.9-6 installed (from debian lenny, i.e. stable). Now sage runs without a hitch mapping the system libraries: $ cat /proc/3283/maps | grep libsqlite 7f95db986000-7f95db9fa000 r-xp 00000000 fe:01 918139 /usr/lib/libsqlite3.so.0.8.6 7f95db9fa000-7f95dbbfa000 ---p 00074000 fe:01 918139 /usr/lib/libsqlite3.so.0.8.6 7f95dbbfa000-7f95dbbfc000 rw-p 00074000 fe:01 918139 /usr/lib/libsqlite3.so.0.8.6 The same works for libfreetype (also with the version from debian stable). --- Update: using the system wide sqlite, all tests pass except one test in devel/sage/sage/graphs/graph_database.py, and the difference looks like one of ordering (i.e. seems a query for a list of graphs returns in a different order for the system wide sqlite). Gonzalo -- 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
