On Mon, Sep 12, 2005 at 12:03:28AM +0200, Sam Ravnborg wrote:
> If the kernel had used a scheme like the following everything could be
> solved by a few -I statements:
>
> include/i386/asm/<what we have in include/asm-i386 today>
> include/ia64/asm/<what we have in include/asm-ia64 today>
> etc.
>
> Then to use ia64 we would just use:
> -Iinclude/ia64
Doesn't solve the problem. We have header pulled from include/linux/*
by asm/foo.h. It contains generic UML stuff _and_ include of regular
asm/foo.h _of_ _the_ _subarch_. Not a UML stuff that varies depending
on the subarch; we want whatever normal i386, amd64, etc. kernel would
get upon include of asm/foo.h.
See what I mean? _IF_ we just wanted subarch foo.h, your scheme would
work. If we wanted subarch-dependent header that would be pulled by
foo.h - ditto (sysdep/blah.h from foo.h). But we can't do that when
we want #include <asm/foo.h> (from arch-independent code) pull some
UML stuff *and* asm/foo.h of subarch.
That's the problem. Everything else is reasonably easy to deal with.
That one is not. And yes, I know about #include_next. I'd rather
stick to C, though, TYVM...
-
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]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |