Re: shared mysqlnd extension ...

Rasmus Lerdorf wrote:

On 08/20/2012 06:51 PM, Lester Caine wrote: Ferenc Kovacs wrote:

why is this an internals question?

Because no one answered on general:( But since the core code base does not compile it seems internal to me anyway. The bundled extensions are not designed to be built standalone using phpize as you have discovered. The core codebase builds perfectly using the procedure it was designed for. And you don't have to touch your core install. Just add the flags or build in a separate directory if you are worried and type make install-modules and it will install any shared modules from that build without touching anything else. Or you can simply copy the modules/*.so files you want to your extension_dir manually.

Except that mysqlnd does not build as a shared module even when doing a full build. mysqli is fine built either way, and a standalone build of mysqlnd creates a module without any warnings, just not one that works, but there seems to be no way to flag from a core build that mysqlnd should be built shared? There is no mysqlnd.so file to copy over, and only a stand alone build seems to have the relevant flag :( SO am I going to have to just create a parallel installation with mysqlnd included statically? Will the thirty odd existing extensions still work with that without having to recompile them? I ask since I understood that the php-config file needed to match the base code, and this would change when rebuilding the base code. In the past I've ended up recompiling everything just to get a working set of extensions. -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk