[SOLVED]Alpine 2.11 configure can't find LDAP openssl or PAM

I've decided I want the improved S/MIME handling of a more current version
of alpine than the "ALPINE 2.02(1266)" installed by urpmi. Specifically there
are some problems related to smime signed documents. I talked about it with
an Alpine guru named Eduardo Chappa:
Anyway as it happens I also have an antiX Linux installation, And from
their Debian repos I got Alpine 2.10, with which at least most of the
smime problems have been resolved. So I decided to give the latest release
from http://patches.freeiz.com/alpine a try.
But when I try to "configure" it in preparation to the "make install"
I'm bumping into this:
I groped around with urpmf & urpmq and insured that I did have these
installed.
Some of which were already installed. But adding the ones that weren't
didn't make a bit of difference to the configure error:
See: http://pastebin.com/sCyesmvw
could anybody tell me which packages provide the stuff the alpine build is
looking for?
Thanks!
of alpine than the "ALPINE 2.02(1266)" installed by urpmi. Specifically there
are some problems related to smime signed documents. I talked about it with
an Alpine guru named Eduardo Chappa:
on May 10, Eduardo Chappa wrote:
> Ok, I looked into it. It is a bug in re-alpine, which Alpine also used to
> have, but I fixed in some earlier alpha version of Alpine (not in version
> 2.11, but it is fixed now and will be fixed in version 2.20). A little bit of
> background: Alpine uses information from the body to verify the signature, a
> part of it comes from some headers that are in the body, some other comes from
> the part written by the person sending the message. The first part is just
> headers, the second is text and together they make the verified part. What
> happens is that Alpine saves the decrypted text, but does not save the
> decrypted headers, so when it gets the headers, it gets encrypted text, and
> that is not what was signed, so it is computing the signature incorrectly,
> which explains why this fails.
>
> This is a problem in re-alpine, not in the sending agent.
Anyway as it happens I also have an antiX Linux installation, And from
their Debian repos I got Alpine 2.10, with which at least most of the
smime problems have been resolved. So I decided to give the latest release
from http://patches.freeiz.com/alpine a try.
But when I try to "configure" it in preparation to the "make install"
I'm bumping into this:
- Code: Select all
checking for setupterm in -ltinfo... no
checking for setupterm in -lncurses... yes
checking for ber_alloc in -llber... no
checking for library containing ldap_init... no
checking for library containing ldap_open... no
configure: Cannot find LDAP functions! Excluding LDAP support.
checking for library containing SSL_library_init... no
configure: OpenSSL libraries NOT found
checking for library containing pam_start... no
configure: error: No PAM support: library files not found
I groped around with urpmf & urpmq and insured that I did have these
installed.
- Code: Select all
pam
openssl
openldap
openssh-ldap
lib64openssl1.0.0
lib64ldap2.l4_2
Some of which were already installed. But adding the ones that weren't
didn't make a bit of difference to the configure error:
See: http://pastebin.com/sCyesmvw
could anybody tell me which packages provide the stuff the alpine build is
looking for?
Thanks!