GNU libtool invariably includes dependent shared objects' library parent directory pathnames in ${LD_LIBRARY_PATH} in wrapper scripts, whereas slibtool does not presently do so. This non-conformant behaviour breaks, inter alia, avahi when built such as to integrate w/ GNOME's GObject Introspection (cf. https://developer.gnome.org/programming-guidelines/stable/introspection.html.en, https://bugs.gentoo.org/show_bug.cgi?id=777894) and given similar corner cases where build systems oblige operating on executable binaries prior to their dependent shared objects having been installed.
${LD_LIBRARY_PATH}
avahi
GObject Introspection
A tentative patch that addresses this is available at https://www.lucioillanes.de/assets/slibtool-0.5.32%2Balways_include_deplibs_ldlibrarypath.patch.
This fixes the following slibtool-related Gentoo package bugs (WIP): https://bugs.gentoo.org/show_bug.cgi?id=777894 https://bugs.gentoo.org/show_bug.cgi?id=779481 https://bugs.gentoo.org/show_bug.cgi?id=778239 https://bugs.gentoo.org/show_bug.cgi?id=778746 https://bugs.gentoo.org/show_bug.cgi?id=778893
Merged as 2a100f3.
Metadata Update from @lalbornoz: - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.