#27260 [Asn]: Apache php5 module with recode support fails
| From: | php at phpee dot com | Date: | Sun, 15 Feb 2004 15:05:47 +0000 |
| Subject: | #27260 [Asn]: Apache php5 module with recode support fails | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-54947@lists.php.net to get a copy of this message | ||
ID: 27260
User updated by: php at phpee dot com
Reported By: php at phpee dot com
Status: Assigned
Bug Type: Apache related
Operating System: Debian Woody stable
PHP Version: 5.0.0b4 (beta4)
Assigned To: sniper
New Comment:
look, I totally agree with you and admit it was stupid from my side not
to read the manual before posting this bug report. But it took me
several hours till I figured out that --with-recode was the problem.
And I'm not going to read the manual about every single module if I use
20 or even more different extensions. Here you agree with me too,
right? A warning in ./configure would have pointed me right away into
the right direction even if it would have be a warning like "recode
failed... don't ask me why!"
Actually ./configure is already pretty "smart" and provides us with
wonderful human readable warnings. - So why not add this other tiny
check to that script?
But anyway, let's stop arguing about that. Keep up the good work and
good luck for RC1 and PHP5's great future!!!
thx.
Previous Comments:
------------------------------------------------------------------------
[2004-02-15 09:49:35] sniper@php.net
Reading the manual page for recode would have saved you from the same
trouble too.
------------------------------------------------------------------------
[2004-02-15 09:13:41] php at phpee dot com
sorry.
> The IMAP extension cannot be used in conjuction
> with the recode or YAZ extensions. This is due
> to the fact that they both share the same
> internal symbol.
so, this means recode is actually of no use at all! Why not trash it
righ away or at least give the user some warning in ./configure?! A
simple warning would have saved me hours and I wouldn't have to bug you
with a bogus bug report.
------------------------------------------------------------------------
[2004-02-15 08:54:14] sniper@php.net
RTFM: http://www.php.net/recode
(is this SO hard to do..?)
------------------------------------------------------------------------
[2004-02-15 07:24:50] derick@php.net
You can make a backtrace just fine, just start apache in single process
mode (-X) from within GDB.
------------------------------------------------------------------------
[2004-02-15 06:53:45] php at phpee dot com
Description:
------------
PHP 5.0.0b4 compiles fine with the following configuration options:
./configure --prefix=/usr/php5 --with-apxs=/usr/bin/apxs
--with-config-file-path=/etc/php5/apache --disable-rpath
--enable-memory-limit --enable-debug --with-layout=GNU
--with-pear=/usr/share/php --enable-calendar --enable-sysvsem
--enable-sysvshm --enable-sysvmsg --enable-track-vars
--enable-trans-sid --enable-bcmath --with-bz2 --enable-ctype --with-db2
--enable-dba --with-iconv --enable-exif --enable-filepro --enable-ftp
--enable-dbase --with-gettext --enable-mbstring --with-pcre-regex
--enable-shmop --enable-sockets --enable-wddx --enable-tokenizer
--with-expat-dir=/usr --enable-yp --with-zlib --with-zlib-dir=/usr
--with-openssl=/usr --with-exec-dir=/usr/lib/php5/libexec
--disable-static --with-curl --with-gd --with-jpeg-dir=/usr
--with-png-dir=/usr --with-freetype-dir --with-ming --with-gmp
--with-mhash --with-mm --with-mysql
--with-mysql-sock=/var/run/mysqld/mysqld.sock --with-pgsql=/usr
--with-snmp --enable-ucd-snmp-hack --with-ttf --with-xsl
--with-flatfile --with-inifile --with-sqlite --with-xmlrpc --with-mcal
--with-ldap=/usr --with-imap=/usr/src/imap-2002e/ --with-recode
Recode support compiles without any errors but it crashes Apache
(1.3.26).
httpd.conf:
LoadModule php5_module /usr/lib/apache/1.3/libphp5.so
Apache doesn't give me any error output, it just fails right after
starting up and doesn't write anything into error.log/syslog or any
other log.
If I remove --with-recode, all works fine with the above
./configuration options.
AFAIK this was working in 500b3.
Actual result:
--------------
I can't get any gdb backtrace as I'm not even able to startup apache.
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=27260&edit=1