From: Bruce Korb <bkorb@gnu.org>
To: guile-devel Development <guile-devel@gnu.org>
Subject: Re: Why is Guile now setting LD_LIBRARY_PATH?
Date: Mon, 10 Sep 2012 17:08:14 -0700 [thread overview]
Message-ID: <504E80EE.5070408@gnu.org> (raw)
In-Reply-To: <504E7C3E.4040407@gnu.org>
On 09/10/12 16:48, Bruce Korb wrote:
>> $ guile --version
>> guile (GNU Guile) 2.0.5
>> Copyright (C) 2011 Free Software Foundation, Inc.
>
> I added a couple of debug printf's after several hours chasing down
> why my program was crashing:
>
>> in main() LD_LIBRARY_PATH='EMPTY'
>> in inner_main() LD_LIBRARY_PATH='/usr/lib64:/usr/lib64/guile/2.0/extensions'
>
> It was crashing because it was linking against a library in /usr/lib64
> instead of /usr/local/lib64. Now I know why.
>
> 1. Why was this done?
> 2. Why no notice? This is *BROKEN*.
>
> libguile needs to be linked with -Wl,-rpath -Wl,/usr/lib64/guile/2.0/extensions
> instead of messing up your client's link/load. ("/usr/lib64" should not be needed.)
>
> Distribution: openSuSE 12.2 (Just in case they are not following your
> build procedures and I need to harass them.)
P.S. the fix seems to be this, though, naturally, I hate it.
static void
inner_main(void * closure, int argc, char ** argv)
{
atexit(done_check);
initialize(argc, argv);
{
char const * p = getenv("LD_LIBRARY_PATH");
if (p != NULL)
putenv("LD_LIBRARY_PATH=");
}
next prev parent reply other threads:[~2012-09-11 0:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-10 23:48 Why is Guile now setting LD_LIBRARY_PATH? Bruce Korb
2012-09-11 0:08 ` Bruce Korb [this message]
2012-09-11 1:59 ` Greg Troxel
2012-09-11 13:12 ` Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2012-09-11 16:21 Bruce Korb
2012-09-13 23:30 ` Bruce Korb
2012-09-14 18:06 ` Mark H Weaver
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=504E80EE.5070408@gnu.org \
--to=bkorb@gnu.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).