statically linking pam
- To: pam-list@xxxxxxxxxx
- Subject: statically linking pam
- From: Shane Canon <scanon@xxxxxxxxx>
- Date: Tue, 27 Dec 2005 14:30:11 -0500
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=Imv8JHaROkx6j1fBtCCeKO9YizzpWVZRKRnh3OOBdm9+1Ii6CVbXf/vqjm5i3bwXbBBrgCwGgfBbxBZrCxatt7TpahgGc62Y91Do17RHRw7eYMaeHZiJquoEbyLPBpTBjhTCEP5bVjo3iWiF3N+WQuWVVucFRWSSwzQy1A/pQ2w=
- Reply-to: Pluggable Authentication Modules <pam-list@xxxxxxxxxx>
- Sender: pam-list-bounces@xxxxxxxxxx
Greetings,
I am attempting to build the pam library so that it can be statically
linked with applications. (This is needed for an architecture that
doesn't support dynamically linked libraries). I have tried this with
both older versions (0.7x) and the latest (0.99). I keep running into
problems. Is this configuration a part of any regression tests? I
need both libpam and the standard set of modules. From what I can
gather, this should "supported", but I'm not having much luck.
With 0.7x I have tried --enable-static-libpam --enable-static-modules.
With 0.99 I tried --enable-static. In some cases the make fails when
an attempt to read _static_module_objects (which doesn't exist yet).
I can touch this file and get the build to proceed a bit further.
However, then it fails with multiple definition errors for various
symbols. Incidentally, I didn't have much luck building 0.99 at all
(both dynmaic and static).
Any feedback or suggestions would be welcome.
--Shane
_______________________________________________
Pam-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/pam-list
[Fedora Users]
[Kernel]
[Red Hat Install]
[Linux for the blind]
[Gimp]