Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:37747
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: softfail (pb1.pair.com: domain zend.com does not designate 64.97.136.140 as permitted sender)
Message-ID: <014f01c8ba86$9ec2ce10$4401a8c0@foxbox>
Reply-To: "Steph Fox" <steph@zend.com>
To: "Hector Santos" <hsantos@isdg.net>,
	"internals" <internals@lists.php.net>,
	"Elizabeth M Smith" <auroraeosrose@shitennou.com>
References: <4832DDC5.7060307@isdg.net>
Date: Tue, 20 May 2008 15:34:31 +0100
Organization: Zend Technologies
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="iso-8859-1";
	reply-type=response
Content-Transfer-Encoding: 7bit
Subject: Re: --with-ereg
From: steph@zend.com ("Steph Fox")

> For PHP 5.3,  you get browscap.obj linking errors.   I don't understand 
> what ereg does, but I found I had to add the option:
>
>   --with-ereg
>
> After buildconf.bat and running configure.js wit the options, and deleting
>
>     del release_ts\ext\standard\brows*.*
>     rd release_ts\ext\ereg /q /s
>
> and it will make and create fine. (BTW, this was a x64 vc8 minimal build).
>
> Is this option a new required minimal build option that should be forced?
>
> Again, i don't know what this ereg stuff does so I can't tell the 
> importance of it or how to fix it, other than adding the above switch.

'This ereg stuff' is important, in that it supports legacy code... it moved 
from ext/standard to ext/ereg in 5_3 in the vague hope that it might be 
possible to move it out to PECL some day. But whoever did it obviously 
missed a bit.

Again, though... you're seeing errors I don't see.

- Steph