From: Ingo Molnar <mingo@elte•hu>
To: "Luck, Tony" <tony.luck@intel•com>
Cc: Dean Nelson <dcn@sgi•com>,
Andrew Morton <akpm@linux-foundation•org>,
Tejun Heo <tj@kernel•org>,
linux-ia64 <linux-ia64@vger•kernel.org>,
linux-next <linux-next@vger•kernel.org>,
LKML <linux-kernel@vger•kernel.org>
Subject: Re: [PATCH] SGI IA64 UV: fix ia64 build error in the linux-next tree
Date: Wed, 11 Feb 2009 21:25:12 +0100 [thread overview]
Message-ID: <20090211202512.GB8283@elte.hu> (raw)
In-Reply-To: <57C9024A16AD2D4C97DC78E552063EA361689D7D@orsmsx505.amr.corp.intel.com>
* Luck, Tony <tony.luck@intel•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
next prev parent reply other threads:[~2009-02-11 20:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-09 16:25 [PATCH] SGI IA64 UV: fix ia64 build error in the linux-next tree Dean Nelson
2009-02-10 21:25 ` Andrew Morton
2009-02-11 15:01 ` Dean Nelson
2009-02-11 15:05 ` Ingo Molnar
2009-02-11 15:12 ` Dean Nelson
2009-02-11 18:58 ` Luck, Tony
2009-02-11 19:33 ` Dean Nelson
2009-02-11 20:25 ` Ingo Molnar [this message]
2009-02-11 12:32 ` Ingo Molnar
2009-02-11 18:49 ` Luck, Tony
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090211202512.GB8283@elte.hu \
--to=mingo@elte$(echo .)hu \
--cc=akpm@linux-foundation$(echo .)org \
--cc=dcn@sgi$(echo .)com \
--cc=linux-ia64@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=tj@kernel$(echo .)org \
--cc=tony.luck@intel$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox