On Mon, Aug 08, 2016 at 05:46:33PM +0200, Geert Uytterhoeven wrote: > Hi Rich, > > On Mon, Aug 8, 2016 at 4:31 PM, Rich Felker <dal...@libc.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 > >> <ge...@linux-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?
Yes, and that's the intended use, but I added support for builtin DTB for use with systems where it's hard to replace the bootloader with one that can pass a DTB. > If yes, can't you remove the dependency on a builtin DTB? > Allowing to build allmodconfig/allyesconfig helps a lot for build coverage. Users should leave builtin-DTB off, but allyesconfig turns it on. Rich
