[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0803131125010.9727@vixen.sonytel.be>
Date: Thu, 13 Mar 2008 11:31:39 +0100 (CET)
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>
cc: linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
Linux/m68k <linux-m68k@...ts.linux-m68k.org>
Subject: Re: linux-next: Tree for March 13
On Thu, 13 Mar 2008, Stephen Rothwell wrote:
> Status of my local build tests is at
> http://kisskb.ellerman.id.au/kisskb/branch/9/. If maintainers want to
> give advice about cross compilers/configs that work, we are always open
> to add more builds.
I noticed you added `m68k-allnoconfig', which fails because of the following
reasons:
- There's no single CPU type enabled, hence we get:
#define FPSTATESIZE error no_cpu_type_configured
- There's no single platform type enabled, hence we get no definition of
NR_IRQS:
#error unknown nr of irqs
Well yes, these are all `features' of allnoconfig :-)
Or should we make sure you cannot build invalid configs like this?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-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@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists