On Thu, 20 Jan 2005, Andrei Zmievski wrote:
What was the reasoning behind the 1.15->1.16 patch for phpize.in? Your
comments say:
- Changed phpize not to require automake and libtool.
- Fixed build system to always use bundled libtool files.
a) To only require autoconf to be installed to be able to use phpize
b) Prevent problems with different libtool versions
This had an unfortunate effect of building shared extensions on Mac OS X as
.dylib shared libraries, instead of dlopen()'able bundles. The bundled libtool
is way old and does not handle this properly, while the new ones do.
Thus we'll nuke the libtool usage in linking on Macosx.
Patch to acinclude.m4 for this solution is here:
http://www.php.net/~jani/patches/acinclude.m4.macosx-shared-modules.patch
(or someone backports the patches from newer libtools to the
bundled files =)
Reason not to bundle newer libtool: It requires buggy autoconf 2.5x.
--Jani
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
