[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20090211202512.GB8283@elte.hu>
Date: Wed, 11 Feb 2009 21:25:12 +0100
From: Ingo Molnar <mingo@...e.hu>
To: "Luck, Tony" <tony.luck@...el.com>
Cc: Dean Nelson <dcn@....com>,
Andrew Morton <akpm@...ux-foundation.org>,
Tejun Heo <tj@...nel.org>,
linux-ia64 <linux-ia64@...r.kernel.org>,
linux-next <linux-next@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] SGI IA64 UV: fix ia64 build error in the linux-next tree
* Luck, Tony <tony.luck@...el.com> 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-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