PHP 4.0 Bug #9534: Inclusion of 'mcrypt' keeps Apache from starting

From: Date: Sat, 03 Mar 2001 05:54:53 +0000
Subject: PHP 4.0 Bug #9534: Inclusion of 'mcrypt' keeps Apache from starting
Groups: php.dev 
Request: Send a blank email to php-dev+get-47835@lists.php.net to get a copy of this message
From: yubby@lanset.com Operating system: Redhat 6.2 PHP version: 4.0.4pl1 PHP Bug Type: mcrypt related Bug description: Inclusion of 'mcrypt' keeps Apache from starting I've been 'rebuilding' my webservers, upgrading from Apache 1.3.12 (and 14)/PHP-4.0.3pl1/libmcrypt-2.4.5/mysql-3.22.32 to Apache 1.3.17/PHP-4.0.4pl1/libmcrypt-2.4.9/mysql-3.23.33 My 'single CPU' Athlon system upgraded fine, but the 2 'dual' Pentium servers (all of them are running Redhat 6.2 2.2.17-14) won't start Apache if I have the '--with-mcrypt' inclusion in my PHP config. Without it, everything works fine. I even tried 'back-reving' libmcrypt to the old version (2.4.5, 2.4.6, 2.4.7, and 2.4.8, by wiping out all of the 'libmcrypt' stuff in /usr/local/lib, and rebuilding) which didn't work either... gdb reports that httpd exited normally (and that there's no 'backtrace') My configuration looks like: ./configure \ --with-config-file-path=/usr/local/apache \ --with-mysql=/usr/local/mysql \ --with-pfpro=/usr/local/signio/linux \ --with-apxs=/usr/local/apache/bin/apxs \ --with-mcrypt ## (this line is EVIL!!) (please help me......waaaah) P.S. Though libmcrypt compiles fine either way, I seem to remember that there might have been a reason to use the --disable-posix-threads option -- Edit Bug report at: http://bugs.php.net/?id=9534&edit=1

« previous php.dev (#47835) next »