Re: 1.6.0 problems with libguilereadline-v-12 and fix

[Rob Browning]

address@hidden (Paul Jarc) writes:

> But how about this: when linking one of Guile's own libraries,
> temoporarily prepend (assq-ref %guile-build-info 'libdir) to
> LD_LIBRARY_PATH or LTDL_LIBRARY_PATH, whichever is searched first.
> Would that satisfy everyone?

I believe the problem is that if we start modifying either
LD_LIBRARY_PATH or LTDL_LIBRARY_PATH (or the attendant libltdl
functions), we won't just affect guile, we'll affect any app linked
against libguile (if we perform the modification in libguile) or any
other library we load that also uses libltdl or dlopen.  If other
libraries or apps also decide to modify LD_LIBRARY_PATH,
LTDL_LIBRARY_PATH, etc., the result wrt shadowing become order
dependent and hard to predict.

Maybe we don't care about that, but I believe that's the major
concern.

-- 
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C  64AE 78FE E5FE F0CB A0AD