From: Andy Wingo <wingo@pobox.com>
To: Jan Nieuwenhuizen <janneke-list@xs4all.nl>
Cc: "Ludovic Courtès" <ludo@gnu.org>, guile-devel@gnu.org
Subject: Re: Relocatable installation
Date: Mon, 31 Jan 2011 22:30:30 +0100 [thread overview]
Message-ID: <m3ei7swykp.fsf@unquote.localdomain> (raw)
In-Reply-To: <1296507337.17905.26.camel@vuurvlieg> (Jan Nieuwenhuizen's message of "Mon, 31 Jan 2011 21:55:37 +0100")
On Mon 31 Jan 2011 21:55, Jan Nieuwenhuizen <janneke-list@xs4all.nl> 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, however.
May I suggest then a bit more rigor in the choice of paths. What paths
does Guile use? Are they entirely taken from argv0, or are they
hard-coded at build time? I'm not opposed to relocatable builds, in
principle, but if you can move Guile around, then it needs to hard-code
no paths in it.
Regards,
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2011-01-31 21:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-29 19:41 cross building 1.9.14 for mingw Jan Nieuwenhuizen
2011-01-29 21:34 ` Ludovic Courtès
2011-01-31 20:16 ` Jan Nieuwenhuizen
2011-01-31 20:44 ` Ludovic Courtès
2011-02-15 10:20 ` Jan Nieuwenhuizen
2011-02-22 8:34 ` Andy Wingo
2011-02-24 9:39 ` Jan Nieuwenhuizen
2011-02-24 10:37 ` Ludovic Courtès
2011-03-04 11:11 ` problems solved by AC_LIB_HAVE_LINKFLAGS [was: cross building 1.9.14 for mingw] Andy Wingo
2011-03-20 8:08 ` Jan Nieuwenhuizen
2011-03-20 8:21 ` Ralf Wildenhues
2011-03-20 8:34 ` Jan Nieuwenhuizen
2011-03-20 8:56 ` Ralf Wildenhues
2011-01-29 21:39 ` Relocatable installation Ludovic Courtès
2011-01-31 20:26 ` Jan Nieuwenhuizen
2011-01-31 20:50 ` Andy Wingo
2011-01-31 20:55 ` Jan Nieuwenhuizen
2011-01-31 21:30 ` Andy Wingo [this message]
2011-01-31 21:49 ` Jan Nieuwenhuizen
2011-01-31 21:00 ` Ludovic Courtès
2011-01-31 21:18 ` Jan Nieuwenhuizen
2011-01-31 22:09 ` Ludovic Courtès
2011-01-31 22:26 ` Jan Nieuwenhuizen
2011-02-14 12:29 ` cross building 1.9.14 for mingw Ludovic Courtès
2011-02-15 10:02 ` Jan Nieuwenhuizen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3ei7swykp.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=janneke-list@xs4all.nl \
--cc=ludo@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).