Re: Re: --with-ereg

From: Date: Tue, 20 May 2008 15:51:06 +0000
Subject: Re: Re: --with-ereg
References: 1 2 3  Groups: php.internals 
Request: Send a blank email to internals+get-37749@lists.php.net to get a copy of this message
hi Hector, On Tue, May 20, 2008 at 5:41 PM, Hector Santos <hsantos@isdg.net> wrote: > Steph Fox wrote: >>> >>> 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 >>> >>> >>> Is this option a new required minimal build option that should be forced? >>> > >> '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. > > ok, thats good. > > So just to confirm (to avoid goose chasing <g>) you are saying you tried the > minimal build options: > > --disable-all > --enable-cli > --enable-cgi > --enable-object-out-dir=. > --disable-ipv6. > > and the current PHP 5.3 CVS built correctly, without errors? No. As Liz and I said earlier, there is a problem in the browscap.c code. The ereg usage has to be replaced by pcre (browser_name_pattern, browser_name_regex management). Cheers, -- Pierre http://blog.thepimp.net | http://www.libgd.org

« previous php.internals (#37749) next »