#2630: Zlib issues
--------------------------------+-------------------------------------------
Reporter: ch...@… | Owner: bdu...@…
Type: task | Status: closed
Priority: normal | Milestone: 6.7
Component: Book | Version: SVN
Severity: normal | Resolution: fixed
Keywords: |
--------------------------------+-------------------------------------------
Comment(by br...@…):
Replying to [comment:21 gespinasse]:
> Using SSLeay (from a perl script), when libz.so does not exist,
If SSLeay-in-perl is having problems when libz.so does not exist, then
SSLeay-in-perl will *also* have problems as soon as the zlib developers
introduce a binary-incompatible libz. This will be have soname libz.so.2,
and everything will continue to work, *except* pieces of broken code like
this. (Existing binaries will use libz.so.1, which will remain as it is
today.)
If you're using dlopen, you *NEED* to open the soname. *NOT* the compile-
time .so file; there is *NO* guarantee that this filename will stay
binary-compatible, and dlopen() *requires* binary compatibility.
In short: this is not a reason to move libz.so; it's a broken piece of
code.
--
Ticket URL: <http://wiki.linuxfromscratch.org/lfs/ticket/2630#comment:22>
LFS Trac <http://wiki.linuxfromscratch.org/lfs/>
Linux From Scratch: Your Distro, Your Rules.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-book
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
