Hi!

My questions to dreamcat four.

I have build php_fpm 0.6.3 from source and noticed that all php modules
compiled in php_fpm binary.
It's make many troubles.
1. How I can enable or disable some php modules?
2. How I can add to php_fpm loading module without recompilation?





--
Ilyas R. Khasyanov
Unix/Linux System Administrator
GPG Key ID: 6EC5EB27 (Changed since 2009-05-12)

On Wed, Sep 23, 2009 at 1:36 PM, Ilyas -- <umask00@gmail.com> wrote:
> Hi!
>
> My questions to dreamcat four.
>
> I have build php_fpm 0.6.3 from source and noticed that all php modules
> compiled in php_fpm binary.

I don't understand fully because this should be the same as all the other php.
Do you have the latest / newest of 0.6.3 ?
Can you give more information / error message ?

> It's make many troubles.
> 1. How I can enable or disable some php modules?

Ah! Did you set the configure flag '--with-config-file-scan-dir' when
you build php first?
This should be the same like other php build targets. Except we compile twice.
The flag should be specified on the first php configure, *not* second
fpm configure.

eg
cd php-src; configure --with-config-file-scan-dir=/etc/php5/conf.d; make
cd fpm-src; configure --with-php-src=etc... ; make

> 2. How I can add to php_fpm loading module without recompilation?

Then you usually put the module's .ini file in the conf-scan-dir.
This is nice to avoid messing around in the php.ini.

dreamcat4
dreamcat4@gmail.com

dreamcat: is it still built the same way, with php-fpm only needing a
vanilla php build?

if so, then it doesn't matter what modules are enabled/disabled/etc.
when you compile php for php-fpm, you can run it against vanilla php
sources and it still works.

On Wed, Sep 23, 2009 at 10:07 AM, dreamcat four <dreamcat4@gmail.com> wrote:
>
> On Wed, Sep 23, 2009 at 1:36 PM, Ilyas -- <umask00@gmail.com> wrote:
>> Hi!
>>
>> My questions to dreamcat four.
>>
>> I have build php_fpm 0.6.3 from source and noticed that all php modules
>> compiled in php_fpm binary.
>
> I don't understand fully because this should be the same as all the other php.
> Do you have the latest / newest of 0.6.3 ?
> Can you give more information / error message ?
>
>> It's make many troubles.
>> 1. How I can enable or disable some php modules?
>
> Ah! Did you set the configure flag '--with-config-file-scan-dir' when
> you build php first?
> This should be the same like other php build targets. Except we compile twice.
> The flag should be specified on the first php configure, *not* second
> fpm configure.
>
> eg
> cd php-src; configure --with-config-file-scan-dir=/etc/php5/conf.d; make
> cd fpm-src; configure --with-php-src=etc... ; make
>
>> 2. How I can add to php_fpm loading module without recompilation?
>
> Then you usually put the module's .ini file in the conf-scan-dir.
> This is nice to avoid messing around in the php.ini.
>
> dreamcat4
> dreamcat4@gmail.com
>

On Wed, Sep 23, 2009 at 9:43 PM, Michael Shadle <mike503@gmail.com> wrote:
>
> dreamcat: is it still built the same way, with php-fpm only needing a
> vanilla php build?

Yes.

> if so, then it doesn't matter what modules are enabled/disabled/etc.
> when you compile php for php-fpm, you can run it against vanilla php
> sources and it still works.

Not so. php-fpm includes the whole of php compiled into it.

The only thing i can think of is if he didn't specify
'--with-config-file-scan-dir' which usually searches the pre-requisite
shared module ini configuration files. Otherwise unlucky to catch and
early 0.6 version, which couldn't load extensions. It has been fixed
for a while now.

dreamcat4
dreamcat4@gmail.com

Do I understand correctly that the system must be running the version of
php, which we compile to build the php-fpm?

And to connect the modules in the process php-fpm I need to install the
modules from the php, which we have compiled in order to compile php-fpm?

Is it true that the resulting binary php_fpm includes all the php and
modules that we compiled with php to build the php-fpm?

On Thu, Sep 24, 2009 at 1:20 AM, dreamcat four <dreamcat4@gmail.com> wrote:

>
> On Wed, Sep 23, 2009 at 9:43 PM, Michael Shadle <mike503@gmail.com> wrote:
> >
> > dreamcat: is it still built the same way, with php-fpm only needing a
> > vanilla php build?
>
> Yes.
>
> > if so, then it doesn't matter what modules are enabled/disabled/etc.
> > when you compile php for php-fpm, you can run it against vanilla php
> > sources and it still works.
>
> Not so. php-fpm includes the whole of php compiled into it.
>
> The only thing i can think of is if he didn't specify
> '--with-config-file-scan-dir' which usually searches the pre-requisite
> shared module ini configuration files. Otherwise unlucky to catch and
> early 0.6 version, which couldn't load extensions. It has been fixed
> for a while now.
>
> dreamcat4
> dreamcat4@gmail.com
>



--
Ilyas R. Khasyanov
Unix/Linux System Administrator
GPG Key ID: 6EC5EB27 (Changed since 2009-05-12)

On Thu, Sep 24, 2009 at 7:42 AM, Ilyas -- <umask00@gmail.com> wrote:
> Do I understand correctly that the system must be running the version of
> php, which we compile to build the php-fpm?

You need the PHP source code and libxml2-dev

> And to connect the modules in the process php-fpm I need to install the
> modules from the php, which we have compiled in order to compile php-fpm?

It is the same for all php, cgi, cli, apache,
This is for extra modules.

> Is it true that the resulting binary php_fpm includes all the php and
> modules that we compiled with php to build the php-fpm?

FPM includes all of the DEFAULT php modules. See $(PHP_GLOBAL_OBJS)
in the Makefile. This is exactly as all php, cgi, cli, apache.

dreamcat4
dreamcat4@gmail.com