On Sat, May 7, 2016 at 12:18 PM, Volker Braun <vbraun.n...@gmail.com> wrote: > You can set it yourself in the environment after moving Sage, this may work > with the aforementioned caveats about conflicts with system libraries. And > change SAGE_LOCAL/lib/sage-current-location.txt to avoid the relocation > error message. But its definitely not the best solution. > > In any case, I don't think saving an hour or two to serve this very special > usage is worth special casing how we build binaries.
Given an existing Sage install in /projects/sage/sage-dev/ built in the standard way, we have, doing the following: time rsync -axH /projects/sage/sage-dev/ sage-dev/ cd sage-dev echo `pwd` > local/lib/sage-current-location.txt ./sage -br # starts quickly (but singular warning) takes about 3 minutes (on SMC). It results in a copy of Sage that seems to work fine for development (not having to even wait for the first 'sage -br'), though there is one single warning displayed when starting up about Singular: salvus@compute7-us:/tmp/sage-dev$ ./sage ┌────────────────────────────────────────────────────────────────────┐ │ SageMath version 7.2.rc1, Release Date: 2016-05-07 │ │ Type "notebook()" for the browser-based notebook interface. │ │ Type "help()" for help. │ └────────────────────────────────────────────────────────────────────┘ ┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓ ┃ Warning: this is a prerelease version, and it may be unstable. ┃ ┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛ // ** Could not open dynamic library: /tmp/sage-dev/local/bin/p_Procs_FieldQ.so // ** Error message from system: /tmp/sage-dev/local/bin/p_Procs_FieldQ.so: undefined symbol: nDivBy // ** Singular will work properly, but much slower. // ** See the INSTALL section in the Singular manual for details. I tested things like modifying Cython code, typing "sage -br", etc., and dragons did not rain fire down on me. -- William P.S. Doctesting is "disturbing" since Sage now always allocates 25GB of virtual memory, which is bizarre: 25626 salvus 20 0 24.504g 243544 52592 R 99.3 0.8 0:19.00 python This happens with every Sage process. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
