2.0.x and glibc-2.0 collisions...

Dan Merillat (dan@merillat.org)
Thu, 29 May 1997 06:35:04 -0400


Ok, this isn't entirely a kernel issue, but here's the problem:
if you include linux/types.h, glibc totally barfs...

Question: which should I protect by what #define/#ifndef pairs?

Right now, I'm checking gnu/types.h for predefines of __NFDBITS,
or __FDMASK etc. What would be the best way to minimize conflict?

Also, why are programs including linux/*? That should be reserved if they
directly interface with the kernel, correct? modules, stuff like procps
perhaps? Is it stupid programmers or was it simply because standard
libc /includes used current linux source for types.h?

--Dan