From: Ken Raeburn <raeburn@raeburn.org>
Subject: Re: dynamic argv0 relocation
Date: Fri, 10 Jun 2005 11:52:09 -0400 [thread overview]
Message-ID: <9d1487b088ac7ed3aea01f0b5c40fb33@raeburn.org> (raw)
In-Reply-To: <87zmty4b0v.fsf@peder.flower>
On Jun 10, 2005, at 09:05, Jan Nieuwenhuizen wrote:
> It would be nice if guile/libguile would have/support dynamic
> relocation based on the location of the executable (be it guile or
> lilypond).
Would configuring Guile with this option break executables linked
against libguile and installed with different prefixes? Or is there
something the application can do (aside from using the same prefix) to
find the Guile code?
> Below is an attempt that works, but I'm not sure about the api nor the
> implementation. What do you think?
I haven't reviewed it closely, but at first glance, you do seem to be
assuming that whoever runs configure doesn't use the --bindir (etc)
arguments, so that you know how to construct $bindir (etc) from a
single prefix string. That's all well and fine, and probably correct
99% of the time, but it might be good to add a check in the configure
script, and error out if one of the directory variables is set to
something other than what's expected.
Ken
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2005-06-10 15:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-10 13:05 dynamic argv0 relocation Jan Nieuwenhuizen
2005-06-10 15:52 ` Ken Raeburn [this message]
2005-06-10 21:49 ` Kevin Ryde
2005-06-11 2:03 ` Ken Raeburn
2005-06-12 4:20 ` Rob Browning
2005-06-15 14:38 ` Jan Nieuwenhuizen
2005-06-17 0:03 ` Kevin Ryde
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=9d1487b088ac7ed3aea01f0b5c40fb33@raeburn.org \
--to=raeburn@raeburn.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).