statically linking pam

[Shane Canon]

Thanks for the quick response.  Even though it is a little
discouraging, its helpful to know where things stand.  If I manage to
get this working I will try to post any procedures or diffs to the
list.  Incidentally, this is need on a Cray X1E which doesn't support
dynamic libraries (it likely never will).  PAM is useful not just for
its dynamic aspects, but also because its a well defined standard that
many authentication mechanisms have working implementations (ldap,
radius, etc).

Thanks again,

--Shane

On 12/27/05, Thorsten Kukuk <kukuk at suse.de> wrote:
> On Tue, Dec 27, Shane Canon wrote:
>
> > 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?
>
> It is not. Since all modern architectures supports dynamic loading
> and static linking is a very bad idea on this, nobody takes care
> about this.
>
> > 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.
>
> It is not supported. The hooks are still there, somebody only needs
> to look at it and try to fix it. But that's not trivial.
>
>   Thorsten
>
> --
> Thorsten Kukuk         http://www.suse.de/~kukuk/      kukuk at suse.de
> SUSE LINUX Products GmbH       Maxfeldstr. 5       D-90409 Nuernberg
> --------------------------------------------------------------------
> Key fingerprint = A368 676B 5E1B 3E46 CFCE  2D97 F8FD 4E23 56C6 FB4B
>
> _______________________________________________
> Pam-list mailing list
> Pam-list at redhat.com
> https://www.redhat.com/mailman/listinfo/pam-list
>