Ken Moffat wrote:
On Tue, 20 Sep 2005, Chris Staub wrote:
I suspect you have linked against the static library (and that Krishna
probably didn't build the static library).
http://developer.momonga-linux.org/viewcvs/trunk/tools/find-zlib
You probably want to use 2>/dev/null when you run it, or tee stdout to
a file, because stderr gets inundated with messages about uninitialized
values in pattern matches (don't remember that from previously, maybe
the latest perl is more demanding).
The definitive text for upgraded packages is usually to be found in the
development book. If you are indeed linked against the static library,
I'd better change the errata.
Ken
Yeah, apparently module-init-tools does link against the static library
(libz.so doesn't show up in ldd output on any of the module-init-tools
programs, on either my gcc4 system (with correct zlib.so.1.2.3 symlink)
or my 6.1 system (with the wrong 1.2.2 symlink)). When I ran ldd on
several programs that *do* link to zlib's shared library (like libpng,
freetype, and fontconfig) they use /lib/libz.so.1 anyway, so maybe it
doesn't really matter...
Of course the symlink should be correct, but I still don't think that's
the cause of the problem being discussed in this thread. As you said,
Krishna probably just didn't build the static library.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
