RE: [PHP-QA] 4.1.2

Hi, I don't doubt you in the fact that nothing changed for mcrypt, my point is, that something that effects mcrypt did change (whether it was mcrypt code or not is irrelevant in the context of my point) with 4.1.2 as the same options work fine with a patched 4.1.1. I don't have the config.log from 4.1.2 to hand as it got deleted, when I have time I will try with 4.1.2 again and get the config.log Thanks, Karl Austin KDA Web Services Ltd. www.kdawebservices.com Virtual and Dedicated Hosting Read Independent Reviews @ www.kdaws.com/reviews.php Tel: 01427 678779 -----Original Message----- From: derick@php.net [mailto:derick@php.net] Sent: 02 March 2002 11:05 To: Karl Austin Cc: 'Zeev Suraski'; php-qa@lists.php.net Subject: RE: [PHP-QA] 4.1.2 Hello, On Sat, 2 Mar 2002, Karl Austin wrote: > I fully understand it wasn't an option, what I was merely trying to > convey was that if a release is going to miss QA out then it should go > out with as little changed as possible to minimise disruption to people > upgrading, I spent a good 3 hours trying to build my usual PHP build on > 3 different servers only to find that it would no longer build with > 4.1.2 because of --with-mcrypt As Rasmus and I said before, mcrypt did not change one single bit, did you check the output of configure.log as I asked you? regards, Derick -- PHP Quality Assurance Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php