[lkml]   [2004]   [Nov]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [RFC] Splitting kernel headers and deprecating __KERNEL__
    On Nov 25, 2004, David Howells <> wrote:

    > ====================== ============
    > include/user/ /usr/include/user/
    > include/user-i386/ /usr/include/user-i386/
    > /usr/include/linux -> user
    > /usr/include/asm -> user-i386

    Although user/ and user-* make a lot of sense within the kernel source
    tree, I don't think these names would be very clear in /usr/include.
    I'd rather use names in /usr/include that more clearly associate them
    with the kernel. Heck, even /usr/include/asm is inappropriate, but
    it's been there for so long that we really shouldn't try to get rid of

    If I had it my way, we'd have, in the kernel tree, userland-aimed
    headers in include/linux/user and include/asm-<machine>/user, and have
    them installed in /usr/include/linux and /usr/include/asm-<machine>.

    This means these headers shouldn't reference each other as
    linux/user/something.h, but rather as linux/something.h, such that
    they still work when installed in /usr/include/linux. This may
    require headers include/linux/something.h to include
    linux/user/something.h, but that's already part of the proposal.

    Alexandre Oliva
    Red Hat Compiler Engineer aoliva@{,}
    Free Software Evangelist oliva@{,}
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 14:08    [W:0.022 / U:44.308 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site