[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Why is Guile now setting LD_LIBRARY_PATH?

From: Bruce Korb
Subject: Re: Why is Guile now setting LD_LIBRARY_PATH?
Date: Mon, 10 Sep 2012 17:08:14 -0700
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120825 Thunderbird/15.0

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)
    initialize(argc, argv);

        char const * p = getenv("LD_LIBRARY_PATH");
        if (p != NULL)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]