On Sun, Jan 12, 2014 at 8:09 PM, Francois Bissey <francois.bis...@canterbury.ac.nz> wrote:
> Relocation. Technically possible. In practise hard to achieve as it involves > rewriting > runpath inside binaries, this is highly OS dependent. The prefix solves > Volker's > LD_LIBRARY_PATH problem at the cost of relocation. Other gain dear to Volker: > we can use any blas/lapack we want. For the record, I view relocation as an important requirement of any build system we adopt. To me, "relocation" means that you can build Sage in /this/directory, then type "mv /this/directory /that/path; /that/path/sage" and have it work, though it may take a while. Obviously, it would be desirable if this isn't a major security risk (I know Volker has pointed out some important issues with this.) Of course, relocation is really a way to solve the problem "build a sage binary once and make it available to other people to install in their home directory". I don't know of any other way to solve that problem. I also don't know if *any* of the non-Sage build systems in this thread support relocation of binaries. -- William -- William Stein Professor of Mathematics University of Washington 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 sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
