From: Bruce Korb <bkorb@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>,
"Guile Development" <guile-devel@gnu.org>
Subject: Re: Why is Guile now setting LD_LIBRARY_PATH?
Date: Thu, 13 Sep 2012 16:30:48 -0700 [thread overview]
Message-ID: <50526CA8.4020801@gnu.org> (raw)
In-Reply-To: <CAKRnqNJ+5t5X6sh85Z9WmGGy8m7N=ZBR7c8vFNnE+-4FpEV20A@mail.gmail.com>
On 09/11/12 09:21, Bruce Korb wrote:
>> Do you have any solutions meeting this criteria in mind?
>
> Wrap your dlopen's in code that pushes the needed values to the environment
I have a better solution that does not require serializing environment
variable access: do your own search. Do full path dlopen-s first,
using the paths you otherwise would have put into LD_LIBRARY_PATH.
If they fail, then fall back to whatever the glibc would otherwise
do (maybe even using LD_LIBRARY_PATH -- it hasn't been touched).
next prev parent reply other threads:[~2012-09-13 23:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-11 16:21 Why is Guile now setting LD_LIBRARY_PATH? Bruce Korb
2012-09-13 23:30 ` Bruce Korb [this message]
2012-09-14 18:06 ` Mark H Weaver
-- strict thread matches above, loose matches on Subject: below --
2012-09-10 23:48 Bruce Korb
2012-09-11 0:08 ` Bruce Korb
2012-09-11 1:59 ` Greg Troxel
2012-09-11 13:12 ` Ludovic Courtès
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=50526CA8.4020801@gnu.org \
--to=bkorb@gnu.org \
--cc=guile-devel@gnu.org \
--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).