On 08/20/2012 08:12 PM, Lester Caine wrote: > 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 :(
mysqlnd is not a standalone extension at all. It is infrastructure code that needs to be linked into your PHP in order for extensions to use it. Once you have that you can load shared mysql, mysqli and pdo_mysql extensions against it. And no, it won't affect other extensions that mysqlnd is there. But again, this is a question for php-install, not internals. This is pretty basic stuff. -Rasmus -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
