Using $ROOT/$PORTAGE_CONFIGROOT when installing samba-3.0.24, if libcap is installed in / (regardless of whether it is in $ROOT), samba configure will detect and link to libcap.so.1. If libcap is not installed to $ROOT, samba will error out when started as it cannot find libcap.so.1. Linking to libcap doesn't appear to be configurable through 'configure --without-libcap' (or whatever), so this bug is probably something to be pushed upstream (not dissimilar to auto-libfam-linking from earlier samba versions). I did not experience this with <samba-3.0.24
Another point of info: If samba is linked to libcap, emerge --depclean can still remove libcap. revdep-rebuild then wants to rebuild samba. Looks like libcap need to be a dep of samba.
My samba 3.0.24 compiles without libcap present, so no use flag or dep appears to be needed.
Added "caps" USE-flag, together with the following line: use caps && export ac_cv_header_sys_capability_h=yes || export ac_cv_header_sys_capability_h=no This should do the job, closing.
(In reply to comment #3) > Added "caps" USE-flag, together with the following line: > use caps && export ac_cv_header_sys_capability_h=yes || export > ac_cv_header_sys_capability_h=no > > This should do the job, closing. > Thanks, looks good, nice fix. You need to add a line to use.local.desc.
Nope, caps is in use.desc.
It is. Mea culpa.
*** Bug 169005 has been marked as a duplicate of this bug. ***