compiling shadow against libpam

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



--lrZ03NoBR/3+SXJZ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Jun 04, 2002 at 12:02:34PM +0200, Thorsten Kukuk wrote:
> On Tue, Jun 04, Tony den Haan wrote:

> > i'm still having trouble building shadow-4.0.3 against libpam. configure
> > will simply bail out when detecting libpam_misc. this because libpam_mi=
sc
> > in turn needs libpam. this can be "fixed" by patching the configure
> > script, but i rather see a proper solution, which i suppose would be
> > somewhere in configure.ac or something. =20

> In Linux-PAM, libpam_misc schould be linked against libpam. That is
> a minor Linux-PAM bug which has no real effect in practice, because
> everybody using libpam_misc also uses libpam.

In what sense is this a bug?  libpam_misc depends on several functions
that are provided by libpam; therefore, it's appropriate to have this
library linked against libpam, and application maintainers should cope
with this sanely.

Steve Langasek
postmodern programmer

--lrZ03NoBR/3+SXJZ
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8/PImKN6ufymYLloRAtlQAKCvbNTZ0SflhrQp/Tylr2gMEObATACfb3ac
3p9KW6lWhCf9cCLZoUvrzEQ=
=XOOH
-----END PGP SIGNATURE-----

--lrZ03NoBR/3+SXJZ--





[Index of Archives]     [Fedora Users]     [Kernel]     [Red Hat Install]     [Linux for the blind]     [Gimp]

  Powered by Linux