Why should they be the same ? glibc gives you a single portable interface
its none of your business what the kernel and glibc talk
> of twisty little passages all different". I find some header files in
> conflict (bunch of network headers) and also find that there are some things
> in each which the package depends on! AAAARRRRRGGGGGG!!!!!!
You shouldnt be mixing kernel and glibc includes, ever. The problem there
has been that glibc doesnt include headers for everything it should have done
and if you find one of those extract it out and write a glibc header for it
Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu