Re: Bug #1396 Updated: Bad lbphp3.module definition for Apache server

> ID: 1396 > Updated by: rasmus > Reported By: lampa@fee.vutbr.cz > Status: Closed > Bug Type: Installation problem > Assigned To: > Comments: > > When building the static PHP module against Apache, there is no way to check which > REGEX implementation is being or will be used. Hence we have to force one or the other. Why? _Some_ regexp package will be included anyway, apache-1.3.x internaly uses regexp (in http_request.c, it's not optional). It's really not necessary to add rule WANTHSREGEX=yes. Or php3 needs to know which regex package is there? > Just about every system will work ok with the HSREGEX version. And for those that do > not work you would build php using --with-system-regex which would then tell Apache > to not use the hsregex implementation. Not quite true. If you compile HSREGEX on FreeBSD, NETBSD, etc. you will get regexp library which doesn't work in localised environment (I've encoutered this). The reason: HSREGEX uses CHAR_MAX from <limits.h> and CHAR_MAX is 127 even if you compile using -funsigned-char on these systems (yes, it's a bug in system header, i've filled bug report). And that is the reason why Apache without php3 module _does not_ use hsregex on these systems. Installation of php3 module breaks this rule. Petr Lampa -- Department of Computer Science and Engineering E-mail: lampa@fee.vutbr.cz Faculty of El. Engineering and Comp. Science Phone: (+420 5) 7275/225,111 Technical University of Brno Fax: (+420 5) 41211141 Bozetechova 2, 612 66 Brno, Czech Republic -- PHP Development Mailing List http://www.php.net/ To unsubscribe send an empty message to php-dev-unsubscribe@lists.php.net For help: php-dev-help@lists.php.net