libcap
Prepare
Section titled “Prepare”- Depends on
linux-headers progs/mkcapshdoc.shdepends onbash
Configure
Section titled “Configure”DEBUGis empty by default- Explicitly specify
CC,AR,RANLIBandOBJCOPYwhenCROSS_COMPILEis defined GOPKGDIRisn’t used whenGOLANG=noINDENTis empty if not found and is not used whenUSE_GPERF=noKERNEL_HEADERScontrol whichcapability.h,prctl.handsecurebits.hto include, the internal ones underlibcap/include/uapi/linuxvs the ones underusr/include/linux(provided bylinux-headers) and these two may not always be in sync which is why the internal headers are “intentionally” kept ahead; do not setKERNEL_HEADERSPTHREADSis set toyesby default and provideslibpsxRAISE_SETFCAPis set tonoby default (yesis not recommended)USE_GPERF=noprevents the build system from depending ongperfand uses the fallback generator insteadCAPSH_SHELL='-DSHELL=\"/bin/sh\"'stopscapshfrom falling back to/bin/bash
- Does not support parallel build; complains about missing
cap_names.hwhen it exists (a race condition probably..)
Package
Section titled “Package”- Are
pam_cap.so,libcap.soandlibpsx.sorunnable as standalone binaries (chmod +x)?