Hi Stephe, On Fri, Mar 13, 2009 at 04:20, Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> wrote: > On Thu, 12 Mar 2009 14:08:57 +0100 Geert Uytterhoeven <geert@xxxxxxxxxxxxxx> wrote: >> >> I can't seem to reproduce the compile failure of kernel/up.c on m68k, >> as shown on >> http://kisskb.ellerman.id.au/kisskb/buildresult/186066/: >> >> | kernel/up.c:16: error: dereferencing pointer to incomplete type > > When kisskb gets an error in building a kernel, it tries to bisect the > problem starting from a known good kernel. The above error occurs > during the bisection process not when building the original kernel. I > guess we need to be a bit more careful when reporting the errors. Sorry > about that. Ah, that explains it, thanks! I had also just noticed kernel/up.o was compiled twice, and the first one succeeded. Now I understand why... Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx 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-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
