pkgsrc-Users archive

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

Problems with security/PAM on Slackware Linux 11.0 using pkgsrc-2007Q2



I get the following errors when building a binary package for PAM on Slackware 
Linux 11.0 using pkgsrc-2007Q2:

pkg_create: can't stat `/usr/pkg/lib/security/pam_cracklib.la'
pkg_create: can't stat `/usr/pkg/lib/security/pam_userdb.la'
=> Registering installation for PAM-0.77nb5
pkg_admin: PAM-0.77nb5: File `/usr/pkg/lib/security/pam_cracklib.la' is in +CONT
ENTS but not on filesystem!
pkg_admin: PAM-0.77nb5: File `/usr/pkg/lib/security/pam_userdb.la' is in +CONTEN
TS but not on filesystem!
PAM-0.77nb5 requires installed package db4-4.5.20.2
PAM-0.77nb5 requires installed package libcrack-2.7nb1
===> Building binary package for PAM-0.77nb5
pkg_create: can't stat `/usr/pkg/lib/security/pam_cracklib.la'
pkg_create: can't stat `/usr/pkg/lib/security/pam_userdb.la'
tar: Unable to access lib/security/pam_cracklib.la (No such file or directory)
tar: Unable to access lib/security/pam_userdb.la (No such file or directory)
tar: WARNING! These file names were not selected:
lib/security/pam_cracklib.la
lib/security/pam_userdb.la
pkg_create: /usr/pkg/bin/tar command failed with code 1
Creating package /usr/pkgsrc/packages/pkgsrc-2007Q2/All/PAM-0.77nb5.tgz
Using SrcDir value of /usr/pkg
Registering conflicts: openpam-[0-9]*.
ERROR: pkg_create -K pkg failed (2)
*** Error code 1

Stop.
bmake: stopped in /usr/pkgsrc/security/PAM
*** Error code 1

Stop.
bmake: stopped in /usr/pkgsrc/security/PAM
*** Error code 1

Stop.
bmake: stopped in /usr/pkgsrc/security/PAM

When I take out the libcrack option it still happens, though only with 
pam_userdb.la.

Slackware, at least my installation of it, doesn't have /usr/include/ndbm.h, so 
it uses db4.  Looking back, the pam_userdb library isn't built at all, and even 
with the libcrack option enabled pam_cracklib isn't built either.

Does anyone have any ideas on how to fix this?  It looks like the dependencies 
are being pulled in through buildlink, but for some reason they're not being 
used.  If you need more details on the build I can provide them.

In the meantime I set PAM_DEFAULT to openpam in my mk.conf file and built 
openpam.  It built just fine.  I'm not sure how well it will work on Linux, 
though.

- Dave V.

Attachment: pgpdmyj06bv3U.pgp
Description: PGP signature



Home | Main Index | Thread Index | Old Index