Re: Re: Latest phpize.in change screws up shared extensions on Mac OS X

PHP-GTK uses a lot of external macros though its extensions, such as AM_PATH_GLIB_2_0(), AM_PATH_GTK_2_0(), and others. Those are contained in .m4 files located in aclocal's share directory and without running aclocal the configuration process fails, since those macros are external. -Andrei On Jan 22, 2005, at 11:28 AM, Jani Taskinen wrote:

    Care to elaborate a bit? Exactly WHAT macros you use?

    --Jani

On Thu, 20 Jan 2005, Andrei Zmievski wrote:

Also, you removed calls to aclocal which presents yet another problem. My shared extension uses external aclocal macros and since aclocal is not run, it cannot locate and bundle them into aclocal.m4. Please fix. -Andrei On Jan 20, 2005, at 11:16 AM, Andrei Zmievski wrote:

Jani, 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. 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.

-Andrei