Re: Putting .so symlinks in libs package for dlopen()ing?
> (BTW does anyone know offhand of a good reference for what's supposed
> to happen when you end up with conflicting shared-lib sub-depends?
> I.e. libfoo -> libbar -> libbaz1
> -> libbax -> libbaz2
> so that libfoo is indirectly linked against two versions of libbaz?
> I've received conflicting info, including some anecdotal evidence
> that libfoo can actually end up with access to a mixture of symbols
> from both versions of libbaz. If true, this would make it extremely
> difficult to actually use a "version check" function to make sure you
> loaded and were calling functions from the version you expected...)
> Thanks, and hope this helps.
There is an option when dlopening whether you want to export that
symbol to the other shared libs, to resolve whether -Bsymbollic-ly, or
-Bshared-ly, and the default was to -Bshared.
GNOME1/GTK1.2 experienced problems when GTK+ 1.2 applications were
linked with libpng3, some pixmap theme engines (which were dlopened)
were linked with libpng2, and they were dlopened with RTLD_GLOBAL.