Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:50145
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain schlueters.de from 217.114.211.66 cause and error)
To: =?ISO-8859-1?Q?J=E9r=F4me?= Loyet <jerome@loyet.net>
Cc: php-dev <internals@lists.php.net>
In-Reply-To: <AANLkTi=Mg5cYU9tRtPOZ-u-D_Kx9s0_0z94-25L9FXOw@mail.gmail.com>
References: <AANLkTi=Mg5cYU9tRtPOZ-u-D_Kx9s0_0z94-25L9FXOw@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Date: Thu, 11 Nov 2010 18:15:41 +0100
Message-ID: <1289495741.9157.47.camel@guybrush>
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] [PHP] multiple sapi (multiple bug reports)
From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=)

Hi,

On Thu, 2010-11-11 at 17:36 +0100, Jérôme Loyet wrote:
> there is several bug reports about having problem compiling differents
> SAPI at once.
> 
> http://bugs.php.net/52419
> http://bugs.php.net/48989
> http://bugs.php.net/53271
> 
> I'm also experiencing the same problem. CLI can be compiled and build
> with any other SAPI. But only one other SAPI could be compiled and
> build at once.
> 
> If this is a normal behaviour, we should add an error at configure
> telling that only one SAPI is supported at once.
> It not, we should correct it.

Building multiple SAPIs should only be "required" by distributors who
want to save compile time. CLI is a special exception to this rule. 

I was under the impression that a conflict might be due to the way
main/internal_functions.c is generated, while I noticed that modules
belonging to a SAPI (like the one holding apache-specific functions)
aren't registered via that file but directly from within the SAPI. (For
CLI there is a special case with internal_functions_cli.c which lists
extensions like realdine which can only be added to CLI)

There might be other conflicts though so I would be careful with adding
support for this.

johannes