FS#56623 - [libcap] dependency on PAM for test.c
Attached to Project:
Arch Linux
Opened by Andreas Baumann (andreas_baumann) - Thursday, 07 December 2017, 21:01 GMT
Last edited by Eli Schwartz (eschwartz) - Thursday, 07 December 2017, 22:26 GMT
Opened by Andreas Baumann (andreas_baumann) - Thursday, 07 December 2017, 21:01 GMT
Last edited by Eli Schwartz (eschwartz) - Thursday, 07 December 2017, 22:26 GMT
|
Details
Description:
gcc -O2 -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -Dlinux -Wall -Wwrite-strings -Wpointer-arith -Wcast-qual -Wcast-align -Wstrict-prototypes -Wmissing-prototypes -Wnested-externs -Winline -Wshadow -g -L/home/cross/build/libcap/src/libcap-2.25/pam_cap/../libcap -o testcompile test.c pam_cap.o -lpam -ldl -L../libcap -lcap test.c:3:10: fatal error: security/pam_modules.h: No such file or directory #include <security/pam_modules.h> ^~~~~~~~~~~~~~~~~~~~~~~~ compilation terminated. 'pam' is not part of base or base-devel Sadly the test is also build if --nochech is specified with makepkg. So, technically depends=('pam') is currently needed, maybe it's worth reporting this upstream? Additional info: * package version(s): 2.25-1 * config and/or log files etc. Steps to reproduce: makepkg -si without pam installed (ok, this is hard, unless you cross-compile into an almost empty pacman root with only the packages of depend=() installed). |
This task depends upon
Closed by Eli Schwartz (eschwartz)
Thursday, 07 December 2017, 22:26 GMT
Reason for closing: Not a bug
Additional comments about closing: pam is pulled in by multiple things in base-devel as well as base.
Thursday, 07 December 2017, 22:26 GMT
Reason for closing: Not a bug
Additional comments about closing: pam is pulled in by multiple things in base-devel as well as base.
Comment by Jan de Groot (JGC) -
Thursday, 07 December 2017, 22:22 GMT
pam is in base (it's a dependency for shadow which is in base),
but libcap is also in base (it's a dependency for coreutils). pam
should be a makedepend for libcap.