Hi Thanks for taking the time to help me learn.
On 4 February 2016 at 16:15, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote: > On 2016-02-04 15:09, Jan Groenewald wrote: > >> But can I say most binaries should not have hard-coded paths patched >> just after compilation? >> > You are right, but only because "most binaries" are compiled with the > correct path in the first place. You have that option with Sage: if you > compile everything in the destination directory to begin with, everything > will work fine. > Most developer and science software are compiled in place. Nothing on my Debian, Ubuntu, Fedora, Redhat, etc. systems are compiled in place. The files are put there by a package manager. I can't move a binary but I can move a package. 0 jan@kontiki:~$cp /usr/lib/firefox/firefox .; ./firefox # <-- one binary without libs Could not find the Mozilla runtime. 255 jan@kontiki:~$rm firefox 0 jan@kontiki:~$cp -R /usr/lib/firefox .; ./firefox/firefox # folder with interdependent libraries and relative paths 0 jan@kontiki:~$# worked! 0 jan@kontiki:~$ 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. Does sage not ever hope to get to that (despite me not knowing the build process and non-trivial work involved in this? The binary patching is a second option if you don't want hardcoded paths in > the binary you download. hardcoded absolutenot relative (to SAGE_ROOT) 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.
