Le jeudi 24 mars 2005 à 14:37 +0100, Bartosz Fenski aka fEnIo a écrit :
> [ sid / unstable ]
>
> ([EMAIL PROTECTED])~$ldd /usr/lib/libSDL.so
> libartsc.so.0 => /usr/lib/libartsc.so.0 (0x40103000)
> libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 (0x40109000)
> libgthread-2.0.so.0 => /usr/lib/libgthread-2.0.so.0 (0x4010e000)
> libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0x40113000)
> libesd.so.0 => /usr/lib/libesd.so.0 (0x40193000)
> libaudiofile.so.0 => /usr/lib/libaudiofile.so.0 (0x4019b000)
> libaudio.so.2 => /usr/lib/libaudio.so.2 (0x401bf000)
> libXt.so.6 => /usr/X11R6/lib/libXt.so.6 (0x401d4000)
> libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x40226000)
> libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x402ed000)
> libvga.so.1 => /usr/lib/libvga.so.1 (0x402fb000)
> libaa.so.1 => /usr/lib/libaa.so.1 (0x40360000)
> libasound.so.2 => /usr/lib/libasound.so.2 (0x4037c000)
> libm.so.6 => /lib/libm.so.6 (0x4042f000)
> libdl.so.2 => /lib/libdl.so.2 (0x40452000)
> libpthread.so.0 => /lib/libpthread.so.0 (0x40455000)
> libc.so.6 => /lib/libc.so.6 (0x404a6000)
> libSM.so.6 => /usr/X11R6/lib/libSM.so.6 (0x405d9000)
> libICE.so.6 => /usr/X11R6/lib/libICE.so.6 (0x405e2000)
> libncurses.so.5 => /lib/libncurses.so.5 (0x405fa000)
> libslang.so.1 => /lib/libslang.so.1 (0x40639000)
> libgpm.so.1 => /usr/lib/libgpm.so.1 (0x406ac000)
> /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)
> ([EMAIL PROTECTED])~$
>
> [ sarge / testing ]
>
> ([EMAIL PROTECTED])~$ldd /usr/lib/libSDL.so
> libm.so.6 => /lib/libm.so.6 (0x400ad000)
> libdl.so.2 => /lib/libdl.so.2 (0x400cf000)
> libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x400d2000)
> libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x4019a000)
> libpthread.so.0 => /lib/libpthread.so.0 (0x401a8000)
> libc.so.6 => /lib/libc.so.6 (0x401f9000)
> /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)
> ([EMAIL PROTECTED])~$
Sarge and sid have the same SDL version. You are basically comparing
libsdl1.2debian-all and libsdl1.2debian-oss.
> Any reason for such huge disproportions? That's where we got libglib2.0.
> Scorched3D built on sarge works fine and doesn't link against libglib2.0.
That's an indirect dependency (brought by libarts), that you won't see
if you pass --as-needed to ld. However, this is not enough, as users
having libsdl1.2debian-{all,arts} installed will still get this
dependency at runtime, probably leading to segfaults.
> Also seems that other distros have wxgtk2.4 linked against libglib2.0 and
> libsdl doesn't linked against any libglib.
> This way most other distros have scorched3d linked against libglib2.0, but
> only because wxgtk2.4 and not libsdl.
This may be because they are building a GTK+2.0 version of libwxgtk2.4.
> I'm not sure what to do now. Is it possible to link our wxgtk2.4 against
> glib2.0? Or unlink libsdl from using libglib?
I'm afraid there is no miracle solution. Getting wxgtk2.5 to install
together with wxgtk2.4, if possible, would be a good option. IIRC, it's
possible to rebuild WxWidgets 2.4 against GTK+ 2.x, but it requires
changes in the applications because of the move to UTF8.
--
.''`. Josselin Mouette /\./\
: :' : [EMAIL PROTECTED]
`. `' [EMAIL PROTECTED]
`- Debian GNU/Linux -- The power of freedom
