Re: just how "sanitized" are the sanitized headers?

On 11/30/06, Robert P. J. Day <rpjday@xxxxxxxxxxxxxx> wrote:
i noticed that, when i generate the sanitized headers with "make
headers_install", there are still a number of headers files that are
installed with variations on "#ifdef __KERNEL__".

i always thought the fundamental property of sanitized headers was
to be compatible with glibc

You were wrong.

and have no traces of "KERNEL" content
left.

That's correct.

so what's the purpose of leaving some header files with that
preprocessor content?

When you see __KERNEL__ in sanitized headers, it's either due to
a) unifdef bug, or
b) header being listed in header-y when it should be listed in unifdef-y
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Relevant Pages

  • Re: just how "sanitized" are the sanitized headers?
    ... headers_install", there are still a number of headers files that are ... i always thought the fundamental property of sanitized headers was ... having never worked with unifdef before, i guess i was being overly ...
    (Linux-Kernel)
  • Re: Simple header cleanups
    ... belief the header set would be quite small (probably an order of magnitude ... smaller than the "sanitized headers" package). ...
    (Linux-Kernel)
  • Re: Conflicts in kernel 2.6 headers and {glibc,Xorg}
    ... > first time with Linux kernel 2.6.10 headers as a base for glibc. ... Linux from Scratch uses sanitized headers; if you want to use raw ... send the line "unsubscribe linux-kernel" in ...
    (Linux-Kernel)