Messages in this thread | | | Date | Fri, 18 Jun 2004 22:49:38 +0200 (MEST) | From | Geert Uytterhoeven <> | Subject | Re: [PATCH] cross-sparse |
| |
On Fri, 18 Jun 2004, Linus Torvalds wrote: > On Thu, 17 Jun 2004, Geert Uytterhoeven wrote: > > I wanted to give sparse a try on m68k, and noticed the current infrastructure > > doesn't handle cross-compilation (no sane m68k people compile kernels natively > > anymore, unless they run a Debian autobuilder ;-). > > > > After hacking the include paths in the sparse sources, installing the resulting > > binary as m68k-linux-sparse, and applying the following patch, it seems to work > > fine! > > Hmm.. It does make sense, but at the same time, sparse isn't even really > supposed to _care_ about the architecture. Especially not for a kernel > build. > > Which part breaks when not just using the native sparse? As far as I know, > a kernel build should use all-kernel header files, with the exception of > "stdarg.h" which I thought was also architecture-independent (but hey, > maybe I'm just a retard, and am wrong).
IIRC, actually the first error I got when using the native sparse was that it couldn't find stdarg.h.
And even the non-native sparse doesn't know about architecture-specific defines like __mc68000__, causing some code paths being wrong. Guess I have to replace them by e.g. CONFIG_M68K.
Gr{oetje,eeting}s,
Geert
-- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds - 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/
| |