capability headers question

[Andreas Jaeger]

Arkadiusz Miskiewicz <misiek@pld.ORG.PL> writes:

> Hi,
> 
> Problem with glibc 2.2.2 vs kernel 2.4 (2.2 is ok) headers:
> 
> #include <string.h>
> #include <sys/capability.h>

sys/capability.h?  That's not part of glibc.

> int main() { return 0; }
> 
> [misiek@arm misiek]$ gcc -O2 test.c -o /dev/null
> In file included from /usr/include/linux/fs.h:23,
>                  from /usr/include/linux/capability.h:17,
>                  from /usr/include/sys/capability.h:24,
>                  from test.c:2:
> /usr/include/linux/string.h:12: parse error before `__extension__'

If you mix kernel and glibc headers, you might get problems.  This
doesn't look like a glibc bug.

Andreas
-- 
 Andreas Jaeger
  SuSE Labs aj@suse.de
   private aj@arthur.inka.de
    http://www.suse.de/~aj