guile-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Relocatable installation


From: Ludovic Courtès
Subject: Relocatable installation
Date: Sat, 29 Jan 2011 22:39:42 +0100
User-agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.2 (gnu/linux)

Hi Jan,

Jan Nieuwenhuizen <address@hidden> writes:

> From ed1507425da819363cc6592ee033076838c82051 Mon Sep 17 00:00:00 2001
> From: Jan Nieuwenhuizen <address@hidden>
> Date: Sat, 29 Jan 2011 17:31:17 +0100
> Subject: [PATCH 1/4] Add dynamic relocation support, default off.
>
> 2005-06-08  Jan Nieuwenhuizen  <address@hidden>
>
>       * configure.in: Add --enable-relocation option.  Default off.
>
> libguile/ ChangeLog
>
> 2005-06-09  Jan Nieuwenhuizen  <address@hidden>
>
>       Experimental relocation patch.
>
>       * load.c (scm_init_argv0_relocation)[ARGV0_RELOCATION]: New
>       function.
>
>       (scm_init_load_path)[ARGV0_RELOCATION]: Use it.
>
>       * load.c (scm_c_argv0_relocation)[ARGV0_RELOCATION]:
>
>       * guile.c (main)[ARGV0_RELOCATION]: Use it to append from
>       executable location derived scm library directory.
>       [__MINGW32__|__CYGWIN__]: Append directory of executable to PATH.

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 work.  And some of them are hardcoded in the binary,
as is usual with the GNU Build System.

Furthermore, I think all these paths cannot be reliably inferred from
argv[0].  For instance because libdir doesn’t have to be $bindir/../lib.
It doesn’t seem to fit well in the GNU software installation process.

Still I’d be glad to hear arguments for and against.  :-)

Thanks,
Ludo’.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]