Yes. BUT. I *think* the problem that Michel ran into is this: MIT krb5 by DEFAULT builds static libraries AND, pam_krb5 will link against the static libraries if shared ones aren't available. I don't think the autoconf stuff in CVS pam_krb5 can detect the *lack* of shared krb5 libs. Nico On Fri, Apr 06, 2001 at 04:14:46PM -0500, Steve Langasek wrote: > On Fri, 6 Apr 2001, Nicolas Williams wrote: > > > Make sure you've compiled everything with -fpic or -Kpic or whatever > > your compiler's flag is that turns on position independent code. > > <plug> > The code in sourceforge CVS uses autoconf, and should automatically handle > setup of both the PIC compiler flag and the rpath (-R option). > </plug> > >:) > > > And make sure you link against shared Kerberos libraries. MIT krb5 can > > only be configured to build static or dynamic libraries (see > > --enabled-shared option to ./configure). So watch out. > > It won't help you correct problems with non-PIC code in library dependencies, > though.:/ > > Steve Langasek > postmodern programmer > > > > _______________________________________________ > > Pam-list@redhat.com > https://listman.redhat.com/mailman/listinfo/pam-list --
