On Fri, 28 Apr 2006, Adrian Bunk wrote:
>
> I do still not get your point.
>
> The ABI headers will be used by C libraries.
>
> And by some programs doing low-level Linux specific things - but these
> are exceptions.
>
> Normal userspace programs will simply not care about the contents of the
> kernel ABI headers - the libc will present them pretty headers adhering
> to all past, current and future standards.
As long as that is clear - that the kernel ABI headers are _never_ seen by
normal programs, even indirectly #include'd from the standard include
headers.
That means that any library implementation still needs to basically
_duplicate_ all the kernel ABI structures etc.
Last I heard, a lot of people wanted to avoid that duplication, and
actually wanted the kabi headers exactly because they wanted just _one_
place for these things.
And I suspect a lot of people still think the kabi headers would be
exactly that: things that get #include'd indirectly from the normal header
files.
My point would be that we can't do that. Ever.
As long as people realize that any kabi headers would only ever be used by
system libraries _internally_ to build themselves (or strange system
tools, of course), then I'm happy. I just get the feeling that people
don't always realize that, and they really want to see it as some kind of
"/usr/include/bits" kind of thing.
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
