Re: A couple of shared dependencies that aren't quite right in 4.3.1 wrt zlib and pcre

The problem is it's already deployed in a configuration that's worked in all previous versions. I'm reluctant to break this because it means changing thousands of users configuration settings. Either way though the build process needs fixing, either making them not available for shared build, or doing the right thing when someone specifically asks for shared build (IE --enable-all=shared will still cause static compile, but --enable-all=shared and --with-zlib=shared will cause a shared object). --On Saturday, April 19, 2003 11:43 AM +0100 Wez Furlong <wez@thebrainroom.com> wrote:

There are such notes, but in the php-dev mailing list archives. It is not recommended to build zlib or pcre as shared extensions, as it will disable some features of the core. If you are cooking up a build for shared hosting, the following extensions should be built as static extensions (if you are planning to deploy them at all) in order to retain maximum fuctionality: zlib pcre openssl --Wez. On Fri, 18 Apr 2003, Michael Loftis wrote:

In main/SAPI.c on lines 33,524, and 672 PHP checks for HAVE_ZLIB when it needs to check for HAVE_ZLIB && !defined(COMPILE_DL_ZLIB) because otherwise we now get missing symbols when linking. This makes --with-zlib=shared impossible. ext/standard/image.c makes similar mistake(s) and who knows what else... Theres a similar issue with PCRE havign the same problems. Thing is I see no notes anywhere about building them shared being deprecated or broken. -- Michael Loftis Modwest Sr. Systems Administrator Powerful, Affordable Web Hosting -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php

-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php