unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Rob Browning <rlb@defaultvalue.org>
Cc: guile-devel@gnu.org
Subject: Re: dynamic argv0 relocation
Date: Sat, 11 Jun 2005 23:20:01 -0500	[thread overview]
Message-ID: <877jh04366.fsf@trouble.defaultvalue.org> (raw)
In-Reply-To: <a38015ab4a89a9cd3927e3ba6ccc8377@raeburn.org> (Ken Raeburn's message of "Fri, 10 Jun 2005 22:03:14 -0400")

Ken Raeburn <raeburn@raeburn.org> writes:

> I think the thing that makes this case tricky is the Guile library.

You may have already been thinking of these, but in case not, it's
also any other libraries provided by Guile (srfi 13/14) or by any
external modules, and while the Guile library has to be somewhere that
ld.so looks, the other libtool loaded libraries have to be somewhere
that libtool's libltdl looks.  These are similar, but I believe may
not always be the same.  (Does liblttdl look in /usr/local/lib by
default now?).

In any case, I'd be hesitant to start automatically modifying the
environment unless we're *really* sure that what we're doing is the
right thing.  For example, prepending something to PATH or
LD_LIBRARY_PATH may alter a user's intentional ordering and may change
the effective versions of other libs or executables in undesirable
ways.

Of course these comments are most directly applicable to traditional
unix-like OSes.  I'm sure it's possible that we might need to do
arrange things differently on other platforms, but if so, I'd like to
try to make sure that it's clear what the appropriate solution is, and
that those with sufficient experience with the platform (i.e. probably
not me) have adequately considered any corner cases.

-- 
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592  F9A0 25C8 D377 8C7E 73A4


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2005-06-12  4:20 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 [this message]
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=877jh04366.fsf@trouble.defaultvalue.org \
    --to=rlb@defaultvalue.org \
    --cc=guile-devel@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).