[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 8 Aug 2016 17:46:33 +0200
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: Rich Felker <dalias@...c.org>
Cc: Linux Kernel Development <linux-kernel@...r.kernel.org>,
Yoshinori Sato <ysato@...rs.sourceforge.jp>,
Linux-sh list <linux-sh@...r.kernel.org>
Subject: Re: Build regressions/improvements in v4.8-rc1
Hi Rich,
On Mon, Aug 8, 2016 at 4:31 PM, Rich Felker <dalias@...c.org> wrote:
> On Mon, Aug 08, 2016 at 10:38:07AM +0200, Geert Uytterhoeven wrote:
>> On Mon, Aug 8, 2016 at 10:32 AM, Geert Uytterhoeven
>> <geert@...ux-m68k.org> wrote:
>> > + error: No rule to make target arch/sh/boot/dts/.dtb.o: => N/A
>>
>> sh-allyesconfig, sh-allmodconfig
>
> I saw this. Is there any canonical way I should fix this? The problem
> is that there's no default for the DTS name, but I'm not sure there
> should be a default. Getting a hard-coded DTB for a particular board
> when you do allyesconfig seems like a worse UX than getting a build
> failure.
Do you have a way to pass a DTB from the bootloader, like most other
architectures support?
If yes, can't you remove the dependency on a builtin DTB?
Allowing to build allmodconfig/allyesconfig helps a lot for build coverage.
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