Relocatable installation

2011-01-29 Thread Ludovic Courtès
Hi Jan, Jan Nieuwenhuizen writes: > From ed1507425da819363cc6592ee033076838c82051 Mon Sep 17 00:00:00 2001 > From: Jan Nieuwenhuizen > Date: Sat, 29 Jan 2011 17:31:17 +0100 > Subject: [PATCH 1/4] Add dynamic relocation support, default off. > > 2005-06-08 Jan Nieuwenhuizen > > * config

Re: Relocatable installation

2011-01-31 Thread Jan Nieuwenhuizen
Ludovic Courtès schreef op za 29-01-2011 om 22:39 [+0100]: Hi Ludovic, > I’m not sure about this patch. My feeling is that it would take more > than this to allow Guile to be truly relocatable, e.g., all of > $GUILE_LOAD_PATH, $GUILE_LOAD_COMPILED_PATH, $LD_LIBRARY_PATH, > etc. would have to wor

Re: Relocatable installation

2011-01-31 Thread Andy Wingo
Heya Jan, On Mon 31 Jan 2011 21:26, Jan Nieuwenhuizen writes: > I realised we need GUILE_LOAD_COMPILED_PATH too. Added that > in this new patch. I added a bit more explanation: this should > be used together with a sane -rpath $ORIGIN/../lib build. What about the extensions paths? Are all pa

Re: Relocatable installation

2011-01-31 Thread Jan Nieuwenhuizen
Andy Wingo schreef op ma 31-01-2011 om 21:50 [+0100]: Hi Andy, > What about the extensions paths? Are all paths from libpath.h > relocatable? > > Curiously yours, Good question, we [LilyPond installs] never needed/used those, I guess. I can imagine that more paths need to be added, this was s

Re: Relocatable installation

2011-01-31 Thread Jan Nieuwenhuizen
[cc: list] Ludovic Courtès schreef op ma 31-01-2011 om 22:00 [+0100]: Hi, > Your patch lacks this RPATH magic, though. Yes, we have that in our GUB cross build system. Possibly this is a thing/feature request for libtool. > Perhaps it should check > whether ‘-Wl,-rpath='$ORIGIN/../lib'’ works

Re: Relocatable installation

2011-01-31 Thread Andy Wingo
On Mon 31 Jan 2011 21:55, Jan Nieuwenhuizen writes: >> What about the extensions paths? Are all paths from libpath.h >> relocatable? > > Good question, we [LilyPond installs] never needed/used those, > I guess. I can imagine that more paths need to be added, this > was sufficient for guile-1.8,

Re: Relocatable installation

2011-01-31 Thread Ludovic Courtès
Hello! Jan Nieuwenhuizen writes: > Ludovic Courtès schreef op za 29-01-2011 om 22:39 [+0100]: [...] >> I’m not sure about this patch. My feeling is that it would take more >> than this to allow Guile to be truly relocatable, e.g., all of >> $GUILE_LOAD_PATH, $GUILE_LOAD_COMPILED_PATH, $LD_LIB

Re: Relocatable installation

2011-01-31 Thread Ludovic Courtès
Hi! Jan Nieuwenhuizen writes: > Ludovic Courtès schreef op ma 31-01-2011 om 22:00 [+0100]: > > Hi, > >> Your patch lacks this RPATH magic, though. > > Yes, we have that in our GUB cross build system. Possibly this > is a thing/feature request for libtool. > >> Perhaps it should check >> whether

Re: Relocatable installation

2011-01-31 Thread Jan Nieuwenhuizen
Ludovic Courtès schreef op ma 31-01-2011 om 23:09 [+0100]: > I mean, if this feature goes in, then ‘configure’ should check whether > this incantation is supported (it may not work with combinations other > than GCC + GNU ld) and give up if it’s not. Yes, I understand. > When it’s supported, ‘li

Re: Relocatable installation

2011-01-31 Thread Jan Nieuwenhuizen
Andy Wingo schreef op ma 31-01-2011 om 22:30 [+0100]: > May I suggest then a bit more rigor in the choice of paths. Sure. > What paths does Guile use? Good question. I'm rather new to 1.9 series. > Are they entirely taken from argv0 The only thing this reloc patch takes from argv0 is BINDIR