Hi On 4 February 2016 at 23:04, Jan Groenewald <j...@aims.ac.za> wrote:
> Hi > > On 4 February 2016 at 22:58, Volker Braun <vbraun.n...@gmail.com> wrote: > >> On Thursday, February 4, 2016 at 9:45:49 PM UTC+1, Jan Groenewald wrote: >>> >>> Most software go ./configure --prefix=path; make; make install >>> and installs to elsewhere with known paths for shared libraries, or >>> relative paths for in-package libraries and you can move the tree. >>> >> >> The above command will install *absolute paths* for libraries not in >> standard locations. >> >> The actual use is also more complicated, distribution generally try to >> use "make DESTDIR=/stagingpath install" to package files without installing >> them in the prefix. >> >> If the package buildsystem does not support this, distributions often >> fall back to post-link binary modifications as well (e.g. using patchelf) >> >> Conda (which is probably the closest to what Sage is trying to do, namely >> distribute a pre-compiled python stack that can be installed anywhere in >> the home directory) is doing exactly what Sage is now doing. >> > So it seems (with difficulty) Conda patches binaries as well: http://conda.pydata.org/docs/building/meta-yaml.html#relocatable To make them use relative paths...? Regards, Jan -- .~. /V\ Jan Groenewald /( )\ www.aims.ac.za ^^-^^ -- 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.
