ID: 9534
User Update by: [EMAIL PROTECTED]
Status: Open
Old-Bug Type: mcrypt related
Bug Type: Verisign Payflow Pro related
Description: Inclusion of 'mcrypt' keeps Apache from starting

Ooops,  forgot to change the 'type'....

Previous Comments:

[2001-03-06 20:23:50] [EMAIL PROTECTED]
Changing 'bug type' to "PayFlowPro" related (from 'mcrypt' related) since I have found 
that I can include "mcrypt" (and all the other libraries, such as mysql) if I exclude 
the PFP library from Signio.   Have seen that there's another Bug report on this issue 
(#9530) that looks very similar.

I'm now attempting the 'build' using Apache 1.3.19 and mod_ssl-2.8.1-1.3.19


[2001-03-03 17:30:20] [EMAIL PROTECTED]
libmcrypt 2.4.7 works just fine for me.
And yes, you have to configure libmcrypt with --disable-posix-threads



[2001-03-03 00:54:53] [EMAIL PROTECTED]
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 

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:
    --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


Full Bug description available at:

PHP Development Mailing List <>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to