Hello Jani,
Friday, November 14, 2003, 5:15:39 PM, you wrote:
> On Fri, 14 Nov 2003, Sascha Schumann wrote:
>>> I was merely suggesting ways to make it work, or just get rid of it.
>>> This has nothing to do with the fact that when --enable-versioning
>>> is used shared extensions wi
On Fri, 14 Nov 2003, Sascha Schumann wrote:
>> I was merely suggesting ways to make it work, or just get rid of it.
>> This has nothing to do with the fact that when --enable-versioning
>> is used shared extensions will not work. It was just one issue with it.
>
>Either it is worki
> I was merely suggesting ways to make it work, or just get rid of it.
> This has nothing to do with the fact that when --enable-versioning
> is used shared extensions will not work. It was just one issue with it.
Either it is working as expected (symbols are not exported;
shar
On Fri, 14 Nov 2003, Sascha Schumann wrote:
>Guys, --enable-versioning has always been for those who don't
>need shared extensions and who want to run multiple PHP
>versions concurrently. It does not need to suit everyone's
>needs to be useful.
I guess I didn't make it clear
At 17:56 14/11/2003, Sascha Schumann wrote:
Guys, --enable-versioning has always been for those who don't
need shared extensions and who want to run multiple PHP
versions concurrently. It does not need to suit everyone's
needs to be useful.
I agree completely.
Zeev
--
PHP Interna
Guys, --enable-versioning has always been for those who don't
need shared extensions and who want to run multiple PHP
versions concurrently. It does not need to suit everyone's
needs to be useful.
- Sascha
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscrib
Heh, too bad I remembered this mail after spending some hours
trying to get php4 + php5 work as DSO on same apache. :)
I have both enabled now and it actually works.
(used libtool 1.5 and had to patch sapi/apache/mod_php5.c a bit)
Anyway, the issue with shared modules
