Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:55170
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain fedoraproject.org from 217.70.183.196 cause and error)
Message-ID: <4E632471.7030007@fedoraproject.org>
Date: Sun, 04 Sep 2011 09:10:41 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:6.0.1) Gecko/20110901 Thunderbird/6.0.1
MIME-Version: 1.0
To: PHP Internals <internals@lists.php.net>
References: <4E61EE07.8030402@lsces.co.uk> <1315053753.2311.15.camel@guybrush>
In-Reply-To: <1315053753.2311.15.camel@guybrush>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Why does mysqlnd get included in Linux 'core' PHP5
 packages?
From: remi@fedoraproject.org (Remi Collet)

Le 03/09/2011 14:42, Johannes Schl=C3=BCter a =C3=A9crit :
> Now there is one consequence: If mysqlnd is used it will be built
> statically in PHP, even on Unix, even if the other MySQL modules are
> built shared. This can be fixed by adding a specific configuration
> option to enforce mysqlnd being build as its own shared .so, too.

This will be great.

For RPM, php is build 1 time for each sapi (apache, cli, ...) but
extension are only build once (well twice in we also build zts).

This is ok with libmysql.
If we want to switch to mysqlnd (for RPM), this will imply to build
mysqlnd for each sapi (don't find a flag for this except also building
mysql or mysqli extensions) and so provide various copy of the "static"
library (in the various binaries).

Having mysqlnd as a shared library will also allow to provides easily
mysql/mysqli build with both mysqlnd and libmysql and give the final
user the choice.


Regards,
Remi.