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

[prj@po.cwru.edu (Paul Jarc)]

Greg Troxel <gdt@ir.bbn.com> wrote:
> I really don't understand why people think it is a good idea for guile
> to go searching in the default list of library places for
> libguilereadline-v-12.so.  The only justification I have heard is that
> this is the default behavior of dlopen, and that shared libraries tend
> to work that way.

"Tend to" is right - for ELF, it's possible to force linking to a
fixed path even with ld.so, at least if ld supports -soname.  (AFAIK
only GNU ld does.)  You can set the soname to the full path, and
that's what will be embedded in the executable and used by ld.so.
ld.so will not search the usual places in this case.  But this means
that you cannot set LD_LIBRARY_PATH to run the tests before
installing; the libraries must be installed before the program will
run at all.  So this strategy is useful only when the libraries belong
to a different, already-installed package, or when the installation
prefix is dedicated to this installation of this package so it's safe
to install before testing.

I'm not saying that Guile should do this, BTW.  Just pointing out
something I find interesting.


paul


_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user