Commit Graph

9 Commits

Author SHA1 Message Date
christos
bbde328be4 Build the modules in two phases:
1. build the static modules first, before libpam so that the static
   libpam can link against the module .a files.
2. build the modules after the dynamic libpam is build, so that the
   dynamic modules can link against the dynamic libpam.
2010-05-03 22:12:32 +00:00
christos
7283382b7f make the dependency to libpam, explicit. Fixes afpd in pkgsrc. From Mark Davies
XXX: Should be pulled up to 4.x and 5.x.
2010-05-03 12:58:09 +00:00
mrg
f7f0bc40ae rename LD32DIR to MLIBDIR. 2009-12-13 08:25:20 +00:00
mrg
6b767a6846 don't set LIBDPLIBS in libpam/modules/Makefile - it is not necessary
and it interferes with the compat lib build.  don't use LIB_ROOT_DIR.
2008-10-27 07:48:27 +00:00
christos
4274cae273 Don't try to build PIC stuff if we cannot do PIC. 2005-02-25 18:26:00 +00:00
lukem
178fb7b023 Use LIBDPLIBS to provide the list of libraries for the modules to depend
upon, because:
 * it's MUCH quicker; no need to calculate the OBJDIRS of every library
   we might require in every subdir.
   (make obj drops from 21s to 3s on my system.)
 * it's more robust when building to a fresh DESTDIR.
2004-12-29 15:04:06 +00:00
christos
bfc0dd3a06 Link with libraries from the source build directory. 2004-12-29 04:16:17 +00:00
thorpej
62953ecba5 Install modules into /usr/lib/security 2004-12-29 00:08:14 +00:00
christos
e7d22a2e64 - NetBSD build glue
- Warning fixes
- RCSID's
2004-12-12 08:18:42 +00:00