Mageia forum

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:

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!

firstly i would say be careful about making/compiling a tarball application on a rpm based install.

make sure your ./configure has --prefix=/opt/appname

as otherwise it will write all over your RPM based install , potentially leaving you having to reinstall at worst.

better still see if someone has built an RPM or a SRPM of the app you want and rebuild the SRPM.

to do this you would run rpmbuild --rebuild application.srpm.

its not always full proof, often one made for one rpm distribution, say suse has different compiler and library paths set, and the spec file needs editing,
but its usually easier than the risk of a make install wreaking your system.

second the rpm's you need to provide for a configure are the -devel versions, as they will include what is required for compiling dependant code.

the versions you have are not for development, but runtime only libraries

PS there is a mageia wiki on this, so check it out

regards peter

wintpe wrote:firstly i would say be careful about making/compiling a tarball application on a rpm based install.

make sure your ./configure has --prefix=/opt/appname

Alpine uses a default prefix of /usr/local, isn't that safe enough?

better still see if someone has built an RPM or a SRPM of the app you want and rebuild the SRPM.

Unlikely. Unless I want an older version. When U Washington itself still developed Alpine there were often links to rpms. But neither of the two remaining projects trying to keep alpine viable
(re-alpine and Eduardo Chappa's efforts at http://patches.freeiz.com/alpine) offer anything
but tarballs for the "make install" process

to do this you would run rpmbuild --rebuild application.srpm.

its not always full proof, often one made for one rpm distribution, say suse has different compiler and library paths set, and the spec file needs editing,
but its usually easier than the risk of a make install wreaking your system.

Funny you mentioned suse, Eduardo mentioned that he builds his on a suse system.

second the rpm's you need to provide for a configure are the -devel versions, as they will include what is required for compiling dependant code.

the versions you have are not for development, but runtime only libraries

OK that makes sense. Though I've been having trouble identifying the relevant package names with the urpmf & urpmq tools. I don't suppose there is a way to limit the copious output to:
"-devel" packages only?

UPDATE: should have thought of it sooner:

Example:

Code: Select all

urpmf --uniq --summary openssl | grep devel

worked for me.

NOTE: I've now installed the Alpine 2.11 tarball on 2 Mageia installations. And on the 2nd one I happened to install the LDAP devel package first...

Code: Select all

urpmi lib64ldap2.4_2-devel

And it pulled in almost everything else I needed as dependencies...

PS there is a mageia wiki on this, so check it out

My imagination must be faulty, I've been unable to come up with the right wiki search terms to find an wiki on identifying the package names of installation tarball dependencies. Perhaps you could tell me the URL of the one your thinking of?
I'd still like to know which wiki item covered this. So that I could try to figure out why I couldn't find it...