From: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: Han-Wen Nienhuys <hanwen@lilypond.org>
Subject: Re: dynamic argv0 relocation
Date: Wed, 15 Jun 2005 16:38:27 +0200 [thread overview]
Message-ID: <8764wfsn18.fsf@peder.flower> (raw)
In-Reply-To: <87ll5hx4py.fsf@zip.com.au> (Kevin Ryde's message of "Sat, 11 Jun 2005 07:49:13 +1000")
Kevin Ryde writes:
> No offence, but it sounds very dubious to me
That's why I added the configure option and compile switch. You do
not want this enabled for well behaved systems. Could you live with
that?
> These things are meant to be settled at the "make all" build stage.
I know, but when installing on Microsoft Windows, or in a user account
using autopackage on Linux, the install prefix is determined at
install time.
> (The gnu standards have bits about that.)
(I really like the gnu standards, but when these where written, was
build time not virtually the same as install time?)
Btw, what bit are you referring to?
> Incidentally, for a normal svr4 system won't you still need
> libguile.so in a location known to the loader? It won't be able to
> find it for the main guile executable otherwise.
Yes, if something like this goes in, we should add that. I only used
this for LilyPond's native Windows port, where wrappers are not really
an option.
Jan.
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.lilypond.org
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2005-06-15 14:38 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
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 [this message]
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=8764wfsn18.fsf@peder.flower \
--to=janneke@gnu.org \
--cc=hanwen@lilypond.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).