* Luck, Tony <tony.luck@xxxxxxxxx> wrote: > > What question was that? Folding back across that distance is not possible > > in a Git workflow. I do regular cross-builds - the build bug did not trigger > > with the ia64 defconfig. > > I'm confused by this, as it definitely triggered for me. Perhaps > my build scripts do things a bit differently. Essentially I do: > > $ for c in `ls arch/ia64/configs` > > do > > cp arch/ia64/configs/$i .config > > yes '' | make oldconfig > > make > > done > > Which takes the default answer for any new questions that crop > up. This enabled the GRU driver in the case of the generic_defconfig, > and so the build failed because of the lack of asm/uv.h hm, my build scripts do (in essence): make mrproper make ARCH=ia64 defconfig hm, GRU is enabled as a module. I generally build the =y items, i.e. the vmlinux. There's around 20 thousand modules enabled in various defconfigs, that's a _lot_ of time to build. Ingo -- 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
