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

[Marius Vollmer]

address@hidden (Paul Jarc) writes:

> > Your suggestions work against the usual means of managing shared
> > libraries, not with them.  I think we should work with them, even if
> > they are slightly broken.
> 
> I think we should fix them.

I wont stop you. ;-)

> 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?

Why is that better than always and system-wide prepending $(libdir) to
LD_LIBRARY_PATH?

> > Instead, you should configure the whole system to look into the right
> > places.
> 
> On my system, each installation of each version of each package gets
> its own unique installation prefix.  I configure each package to find
> the libraries it needs at compile time; LD_LIBRARY_PATH would be
> awfully big if I didn't.

Why is it a problem to have a long LD_LIBRARY_PATH?  You do need a
long PATH already, no?

-- 
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3  331E FAF8 226A D5D4 E405