Hello,
I don’t know where did you find libz.so.2 because according to
www.gzip.org/zlib only exists in version 1.
Anyway, both libz.so.1 and libz.so.2 seem too old or incomplete because
symbols zError and zlibversion are missing.
I suggests you to download libz.1.1.4 from www.gzip.org/zlib for qnx 6.1.3.
regards,
Alain.
Alain Bonnefoy <alain.bonnefoy@icbt.com> wrote:
Hello,
I don’t know where did you find libz.so.2 because according to
www.gzip.org/zlib > only exists in version 1.
Anyway, both libz.so.1 and libz.so.2 seem too old or incomplete because
symbols zError and zlibversion are missing.
I suggests you to download libz.1.1.4 from > www.gzip.org/zlib > for qnx 6.1.3.
Looks like an issue with the shlib. As for the SONAME, that is our SONAME
not the version of the library. When we moved to libc.so.2 we also had
to increment all the shlibs that built against libc so we didn’t break older
applications (ie: app brings in libc.so.1 and libz.so.1, if libz.so.1 was
rebuilt with new libc it will then bring in libc.so.2 - that is bad).
I have entered a PR against zlib. Thanks for the report.
Chris McKillop <cdm@qnx.com> “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/
Hi Chis,
I wonder if it’s a good issue for such libraries.
If you wrote this libz, you should find a different name, if this
library comes from www.gzip.org, you should consider that a libz.so.2
maybe available in the future and will certainly cause some problems
with yours.
Alain.
Chris McKillop a écrit:
Alain Bonnefoy <> alain.bonnefoy@icbt.com> > wrote:
Hello,
I don’t know where did you find libz.so.2 because according to
www.gzip.org/zlib > only exists in version 1.
Anyway, both libz.so.1 and libz.so.2 seem too old or incomplete because
symbols zError and zlibversion are missing.
I suggests you to download libz.1.1.4 from > www.gzip.org/zlib > for qnx 6.1.3.
Looks like an issue with the shlib. As for the SONAME, that is our SONAME
not the version of the library. When we moved to libc.so.2 we also had
to increment all the shlibs that built against libc so we didn’t break older
applications (ie: app brings in libc.so.1 and libz.so.1, if libz.so.1 was
rebuilt with new libc it will then bring in libc.so.2 - that is bad).I have entered a PR against zlib. Thanks for the report.
chris
\
Alain Bonnefoy <alain.bonnefoy@icbt.com> wrote:
Hi Chis,
I wonder if it’s a good issue for such libraries.
If you wrote this libz, you should find a different name, if this
library comes from > www.gzip.org> , you should consider that a libz.so.2
maybe available in the future and will certainly cause some problems
with yours.
No, it is the standard zlib. Just missing some symbols. AFAIK those
missing symbols have been resolved for the next major release.
chris
–
Chris McKillop <cdm@qnx.com> “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/