I don't know but I feel it's wrong to do an == check because people might 
be using this PHP version when 2.4.18 is out.


At 06:47 PM 5/19/2001 +0200, [EMAIL PROTECTED] wrote:
>On Sat, 19 May 2001, Andi Gutmans wrote:
> > >I just committed a fix to the CVS, this solved the problem for me.
> > >libmcrypt 2.4.10 still gives some strange results (encrypted strings like
> > >8 \0's), but it works fine with libmcrypt 2.4.11 (I could not get 2.4.12
> > >to compile here).
> >
> > Do you think this is a bug with libmcrypt or in PHP? Should we have
> > ./configure detect the version and say that you need >= 2.4.11?
>I know almost certain that this bug is in mcrypt, because reinstalling
>(without recompiling PHP) libmcrypt 2.4.10 gives the wrong output again.
>So it's wise to do a check for 2.4.11, but I wonder if we must make it >=
>2.4.11, or == 2.4.11, as I expect that compiling with 2.4.12 gives very
>much trouble (because of an updated libtldl). I can check it as soon as
>2.4.13 is out, but I could not get 2.4.12 compiled on my box within 5
>Derick Rethans
>         PHP: Scripting the Web - www.php.net - [EMAIL PROTECTED]
>              SRM: Site Resource Manager - www.vl-srm.net

PHP Development Mailing List <http://www.php.net/>
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