> 1. Make sure there is a libz.a in /lib or /usr/lib, otherwise you have no > static zlib to link in.
Of course there's an old libz.a there. And it should not matter as we're given the --with-zlib arguments to point the build elsewhere for those libraries. And as seen in the report, it is following those pointers. It's just not using them correctly regarding being told to link against libz.a, not libz.so, with the 'zlib' parameter to config. > 2. Temporarily remove or rename the symlink named exactly "libz.so" in > /lib, /usr/lib, /usr/local/lib and /zlib125/lib (This ensures it cannot > link to the dynamic zlib). No, this appears to be to be a ./config build parameter setup error. Why should user's break their perfectly sound systems in order to work around a bug? If users wanted it to link dynamically against libz, they would have specified 'zlib-dynamic' to ./config. ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
