On Wed, 28 Jan 2004, Andrei Zmievski wrote:
>On Wed, 28 Jan 2004, Jani Taskinen wrote:
>> It creates a static libphp5_core.a which is linked to each build
>> SAPI module / binary. Dunno how you could have same lib loaded
>> by e.g. Apache / Apache2 ?? Or what did you mean? :)
>>
>> >T
On Wed, 28 Jan 2004, Jani Taskinen wrote:
> It creates a static libphp5_core.a which is linked to each build
> SAPI module / binary. Dunno how you could have same lib loaded
> by e.g. Apache / Apache2 ?? Or what did you mean? :)
>
> >The best (ideal) result would be to have one libphp[
On Tue, 27 Jan 2004, Andrei Zmievski wrote:
>On Tue, 27 Jan 2004, Jani Taskinen wrote:
>> Here's what I came up with:
>>
>> http://www.php.net/~jani/patches/multi_sapi_build.patch
>>
>> With the patch applied, I'm now able to build at least
>> apache, cli, cgi and embed SAP
On Tue, 27 Jan 2004, Andrei Zmievski wrote:
>On Tue, 27 Jan 2004, Uwe Schindler wrote:
>> Would be great. The only thing is: We must compile all SAPIs with ZTS
>> enabled... But thats the same on windows.
>
>Well, maybe we can have a ZTS and a non-ZTS version of the core lib.
Yes, but it mak
That is also how the new win32 build system handles it;
you have the option of php5ts.dll or php5.dll.
--Wez.
> >> Would be great. The only thing is: We must compile all SAPIs with ZTS
> >> enabled... But thats the same on windows.
> >
> > Well, maybe we can have a ZTS and a non-ZTS version of th
On Jan 27, 2004, at 12:02 PM, Andrei Zmievski wrote:
On Tue, 27 Jan 2004, Uwe Schindler wrote:
Would be great. The only thing is: We must compile all SAPIs with ZTS
enabled... But thats the same on windows.
Well, maybe we can have a ZTS and a non-ZTS version of the core lib.
That seems like a nice
On Tue, 27 Jan 2004, Uwe Schindler wrote:
> Would be great. The only thing is: We must compile all SAPIs with ZTS
> enabled... But thats the same on windows.
Well, maybe we can have a ZTS and a non-ZTS version of the core lib.
- Andrei
--
PHP Internals - PHP Runtime Development Mailing List
To
At 17:40 27.01.2004, you wrote:
On Tue, 27 Jan 2004, Jani Taskinen wrote:
> Here's what I came up with:
>
> http://www.php.net/~jani/patches/multi_sapi_build.patch
>
> With the patch applied, I'm now able to build at least
> apache, cli, cgi and embed SAPIs on one run.
>
> # .
On Tue, 27 Jan 2004, Jani Taskinen wrote:
> Here's what I came up with:
>
> http://www.php.net/~jani/patches/multi_sapi_build.patch
>
> With the patch applied, I'm now able to build at least
> apache, cli, cgi and embed SAPIs on one run.
>
> # ./configure --disable-
On Mon, 26 Jan 2004, Brian J. France wrote:
>> I have a project where I need to have both Apache SAPI (shared) and
>> embed SAPI (shared) compiled/active at the same time. Is that possible
>> to do at all? Any risk of symbol clashes or other similar problems?
>
>Andrei posted this a while ago, but
Hello Brian,
Monday, January 26, 2004, 10:37:56 PM, you wrote:
>> I have a project where I need to have both Apache SAPI (shared) and
>> embed SAPI (shared) compiled/active at the same time. Is that possible
>> to do at all? Any risk of symbol clashes or other similar problems?
> Andrei posted t
On Jan 26, 2004, at 5:10 PM, Andrei Zmievski wrote:
On Mon, 26 Jan 2004, Brian J. France wrote:
Andrei posted this a while ago, but nobody replied and we have learned
this is it not possible.
With the current state of the code and configuration system what would
it take to do something like this:
On Mon, 26 Jan 2004, Brian J. France wrote:
> Andrei posted this a while ago, but nobody replied and we have learned
> this is it not possible.
>
> With the current state of the code and configuration system what would
> it take to do something like this:
>
> Core PHP code is built into libphpX
13 matches
Mail list logo
