> I.e., you configured with "--disable-libz" and rebuilt, and Ethereal
> now works?
Yes.
> If so, please download the Ethereal 0.9.1 source tarball and configure
> and build it - *without* getting rid of any version of libz (i.e.,
> don't remove the one in "/usr/X11R6/lib", and don't rebuild XFree86,
> before configuring and building Ethereal). It *should* fail in the
> configuration stage, with an
>
> old zlib found when linking with X11 - get rid of old zlib.
>
> error.
I did it.
run configure with no flags.
No configure error, no compilation error, execution error as the 0.9.0 :-(
>> I have two differents statics libz on my system.
>> The first one is on /usr/lib/ and the other on /usr/X11R6/lib/.
>> This second one ( which should be probably the wrong one ) comes from
>> www.xfree.org ( as I needed an update of my X ambient ).
>> The first one comes from the original package of Slackware 8.
>
> I've seen this before on Slackware systems - and possibly on other
> Linux systems.
>
CUT. Thx for explanation ( very clear ).
> Installing the old libz on a system with a newer libz means that
> programs *not* linked with a "-L" flag that includes the directory
> containing X11 libraries will get linked with the new libz, but
> programs that *are* linked with that flag will get linked with the old
> libz.
>
> This means, for example, that Tethereal (which is not an X application)
> will get the new libz, but Ethereal (which *is* an X application on
> UNIX) will get the old libz.
>
> Do you have any non-static libz's? If so, where are they, and is
> Tethereal statically, or dynamically, linked with libz?
/usr/lib/libz.so ( .so.1 .so.1.1.3 )
> If you do, you may only have one in "/usr/lib", not in
> "/usr/X11R6/lib", in which case Tethereal will be dynamically linked
> with the libz in "/usr/lib", but Ethereal will be statically linked
> with the libz in "/usr/X11R6/lib".
Correct.
Maybe using an -L /usr/lib just before -L /usr/X11 flag could workaround the
problem ?
Pigi
