|
php.net | support | documentation | report a bug | advanced search | search howto | statistics | random bug | login |
PatchesPull RequestsHistoryAllCommentsChangesGit/SVN commits
[2001-03-03 17:30 UTC] sniper@php.net
[2001-03-06 20:23 UTC] yubby at lanset dot com
[2001-03-06 20:24 UTC] yubby at lanset dot com
[2001-03-12 20:52 UTC] yubby at lanset dot com
|
|||||||||||||||||||||||||||
Copyright © 2001-2025 The PHP GroupAll rights reserved. |
Last updated: Wed Nov 05 15:00:01 2025 UTC |
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