Messages in this thread | | | From | David Woodhouse <> | Subject | Re: [PATCH] __linux__ and cross-compile | Date | Sun, 20 Jan 2002 16:15:02 +0000 |
| |
bunk@fs.tum.de said: > If your compiler is configured as a cross-compiler everything should > work as expected. If you are trying to compile a Linux kernel with a > gcc that is configured to build binaries for NetBSD this sounds evil.
What if he's trying to build UML to run on NetBSD? What if the best QA'd cross-gcc he has available is a generic arm-elf-gcc and he doesn't want to rebuild and do a full test and release cycle on it just because a handful of the kernel header files assume __linux__ will be defined?
> I don't know (I never tried to compile a *BSD kernel).
If you don't know, who was it that typed 'This is definitely wrong' in your first mail? Your cat?
> But if yes please consider what the following parts of your patch change: > -#ifndef __linux__ > +#ifndef __KERNEL__
Well, if he hadn't explicitly mentioned that he made header files which could be included by userspace use defined(__KERNEL__)||defined(__linux__) then I'd understand what you meant. As it is, I don't. Please explain.
-- dwmw2
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |