[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAMuHMdWRjxAboAA+R91i0WLLofBzNN83G-wFjo6TGqX13HXLYw@mail.gmail.com>
Date: Tue, 8 Mar 2016 11:09:43 +0100
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: Ingo Molnar <mingo@...nel.org>
Cc: kbuild test robot <fengguang.wu@...el.com>,
Thomas Gleixner <tglx@...utronix.de>,
"kbuild-all@...org" <kbuild-all@...org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...e.hu>
Subject: Re: kernel/irq/irqdesc.c:206:2: error: array index in initializer
exceeds array bounds
Hi Ingo,
On Tue, Mar 8, 2016 at 10:21 AM, Ingo Molnar <mingo@...nel.org> wrote:
>> Same comment as before: thou shall not compile kernels for m68k without
>> selecting any platform support.
>
> That should be enforced at the Kconfig level.
I'm fully aware of that ;-)
Unfortunately it's not trivial.
How do you enforce that at least one option from a list of options is enabled?
M68k (with MMU) supports three distinct classes of machines:
1. Coldfire (with Coldfire MMU)
2. Sun-3 (with Sun-3 MMU)
3. Rest (with classic Motorola MMU)
Class 3 contains multiple machine types (cfr. top of arch/m68k/Kconfig.machine)
and at least one of them must be selected.
So far everything I tried conflicted with enforcing the 3 distinct classes.
For nommu, it's simpler, as you can typically support a single platform only,
due to the different platforms (usually) having RAM at different addresses.
Suggestions are welcome....
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
Powered by blists - more mailing lists