Re: libmcrypt install probs (Long - Repost Again)
| From: | Richard Lynch | Date: | Wed, 13 Dec 2000 22:06:37 +0000 |
| Subject: | Re: libmcrypt install probs (Long - Repost Again) | ||
| References: | 1 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-30194@lists.php.net to get a copy of this message | ||
If you haven't tried php-install@lists.php.net yet, that's a better place
for this...
> configure says: checking for init_mcrypt in -lmcrypt... no
> configure says: checking for mcrypt_module_open in -lmcrypt... yes
If your configure output does not have this same no/yes dichotomy, you have
a different problem than this one, so can ignore the solution.
> init_mcrypt is found this time because conftest is linked
against -lkaffevm.
>
> mcrypt_module_open is found again because conftest is linked against
> -lkaffevm and -lltdl.
>
> To get conftest to build in both cases you must always link against -lltdl
> when compiling with -lmcrypt. This solves the first problem of determining
> when init_mcrypt and mcrypt_module_open are available. The second problem
is
> with the algorithm. The algorithm assumes that if init_mcrypt exists, you
> must have 2.2 installed and thus defines HAVE_LIBMCRYPT22. This will keep
> PHP from building if you are using 2.4. My solution was to change
configure
> to always link against -lltdl for the mcrypt tests and to decide that you
> have 2.2 only when init_mcrypt is found and mcrypt_module_open is not.
Try editing configure.in (?)... Make a backup copy first. Dig around for
these things he's talking about, and changing them around to have -lltdl
instead of (in addition to?) -lkaffevm.
> PS - On the site for libmcrypt there is also mcrypt-2.5.5 and other
> versions. Do I need to install this as well as libmcrypt? The READMEs do
not
> seem to indicate this but I thought that I'd make sure.
I dunno. Download it and try, I guess...