Summary: | app-admin/syslog-ng-3.4.2 - In file included from gprocess.c:25:0: gprocess.h:33:30: fatal error: sys/capability.h: No such file or directory | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Ladislav Zitka <archenroot> |
Component: | [OLD] Server | Assignee: | Mr. Bones. (RETIRED) <mr_bones_> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | archenroot |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Ladislav Zitka
2013-09-20 15:42:20 UTC
It cannot be seen from the comments straightforwardly so the easy workaround again: sys/capability.h is coming from libcap development library, so I emerged both libcap and libcap-ng, then emerged explicitly syslog-ng and it resulted in success. (In reply to Ladislav Jech from comment #1) > It cannot be seen from the comments straightforwardly so the easy workaround > again: > sys/capability.h is coming from libcap development library, so I emerged > both libcap and libcap-ng, then emerged explicitly syslog-ng and it resulted > in success. syslog-ng ebuilds have "caps? ( sys-libs/libcap )" in DEPEND, and your build log shows you hade USE=caps, so you should already have had /usr/include/sys/capability.h before syslog-ng was emerged. The only possible scenario where this might go wrong is when emerge somehow got the merge order wrong. reopen if you can reproduce the failure with emerge -ev syslog-ng |