Re: bug in socket.h (and maybe many other kernel headerfiles)
Sean Hunter (sean@uncarved.co.uk)
Sun, 19 Sep 1999 10:38:20 +0100
On Sat, Sep 18, 1999 at 12:32:48PM -0400, Benjamin LaHaise wrote:
> On Sat, 18 Sep 1999, Sean Hunter wrote:
>
> ...
> > ...will compile in gcc but not g++ IIRC. Now strictly in ansi c the
> > above should not be allowed as a statement label (which "case 'd':"
> > is) has to attach to a statement (which there isn't one in this case).
>
> Yes, and almost none of the kernel headers that have inline code should be
> pulled in by libc5. Those that are required (like socket.h) should have
> the code #if'd out.
>
> > This is why (regardless of libc), the kernel headers should not be
> > compiled by a c++ compiler.
>
> If that's the case, please explain how I use the C library from C++ on
> libc5 systems? There are commercial apps that require this -- libc5 is
> not dead yet!
OK, I'm happy to help patch the headers. Could you give me an idea
what constructs are causing problems?
Sean
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/