Re: size of XEmacs binary under Sparc/Solaris 2
Didier Verna <verna(a)inf.enst.fr> writes:
Olivier Galibert <galibert(a)pobox.com> writes:
> Including two different versions on the same library can be quite
> dangerous.
My solaris xemacs binray has duplicate libs too (mainly openwin and
X11R6). It's not the only one ... nearly all of the apps I write have this too
! I've never understood why, and how this can work at all:
Me too! I had always just assumed that the first one listed won. (Or
was it the last one listed?) You can't possibly use both can you? I
mean the function names don't have version numbers in them, so only
one lib would be used. Or would the choice of lib be random for each
function?
The scary thing is that everything appears to be working just fine.
libXt.so.5.0 => /usr/X11/lib/libXt.so.5.0
libXt.so.4 => /usr/openwin/lib/libXt.so.4
libXext.so.5.0 => /usr/X11/lib/libXext.so.5.0
libXext.so.0 => /usr/openwin/lib/libXext.so.0
libX11.so.5.0 => /usr/X11/lib/libX11.so.5.0
libX11.so.4 => /usr/openwin/lib/libX11.so.4
Can somebody give me an explanation ?
I think the openwin libs come from libXm. If you do an ldd on libXm,
you'll see links to openwin. I checked my config, and the link phase
definitely does not use openwin.
I'm thinking that for all of my future builds, I'm just going to
forget about X11R6 and just use the openwin stuff, if I can convince
my setup and config to do so.
Ray