On Fri, Mar 18, 2016 at 5:42 AM, Dima Pasechnik <[email protected]> wrote: >> Yes definitely. It worked very well for precisely this use case for a >> decade. > > > well, it was quite often a source of trouble (I can point to dozens of > requests for help caused by LD_... paths issues), and then it has reached > the point when OSX won't support it.
OS X is not relevant here -- the use case is "build Sage on a Linux server, then make a copy of it on the same server". > Finally, let me point out that the current rpath setup works, and needs just > minor tweaks to become as quick as the old one. > Thus, again, why would you want it back? I want something that actually works efficiently; that's all. From the above report from David it sounds like the current rpath setup doesn't work.[...] > Unfortunately, the relocation script is run at the end of the installation, > making it uncopyable. Maybe you can disable that script in the source code before building Sage? I personally routinely disable sage-location-whatever-it-is these days before doing anything with Sage. I build a system-wide sage that I never move, but relocation scripts are constantly trying to run anyways, due to symlinks, or whatever. You can put "exit 0" (or sys.exit(0)) at the top of whatever script is causing the trouble, so it doesn't run... William -- William (http://wstein.org) -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
