[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Putting .so symlinks in libs package for dlopen()ing?

From: Junichi Uekawa
Subject: Re: Putting .so symlinks in libs package for dlopen()ing?
Date: Fri, 13 Dec 2002 09:39:13 +0900
User-agent: Wanderlust/2.8.1 (Something) SEMI/1.14.3 (Ushinoya) FLIM/1.14.3 (Unebigoryƍmae) APEL/10.3 Emacs/21.2 (i386-debian-linux-gnu) MULE/5.0 (SAKAKI)

> (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.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]