From: "Jesse Brandeburg" <jesse.brandeburg@gmail.com>
To: "Sam Ravnborg" <sam@ravnborg.org>
Cc: "Linux-Kernel," <linux-kernel@vger.kernel.org>
Subject: Re: git head x86_64 build breakage
Date: Tue, 27 Jun 2006 17:25:05 -0700 [thread overview]
Message-ID: <4807377b0606271725u678901a1h8d9d6776b82db3b4@mail.gmail.com> (raw)
In-Reply-To: <20060627214306.GB372@mars.ravnborg.org>
On 6/27/06, Sam Ravnborg <sam@ravnborg.org> wrote:
> On Tue, Jun 27, 2006 at 01:10:02PM -0700, Jesse Brandeburg wrote:
> > using a fresh pull of Linus' git, I can't build a kernel right now
> > I get this:
> > make O=../2.6.18.obj/ all -j5
> > GEN /home/jbrandeb/2.6.18.obj/Makefile
> > scripts/kconfig/conf -s arch/x86_64/Kconfig
> > init/Kconfig:3: unknown option "option"
> > make[3]: *** [silentoldconfig] Error 1
> > make[2]: *** [silentoldconfig] Error 2
> > make[1]: *** [include/config/auto.conf] Error 2
> > make: *** [all] Error 2
> >
> > reverting to the v2.6.17 init/Kconfig fixes it.
> Look like you did not get kconfig rebuild.
> Try to delete scripts/kconfig/* in your ../2.6.18.obj/ directory and let
> me know if this fixes it.
> It this is a proper fix I need to look into why kconfig binaries was not
> rebuild.
Ah, that worked, I was definitely re-using a directory I had built in
before. I guess maybe it didn't figure out the dependency somehow.
so to repro (this is pseudo-git, i couldn't figure out how to test
this without starting all over)
git checkout v2.6.17
make O=../foo.obj all
git checkout HEAD
make O=../foo.obj all
<boom>
Thanks!
Jesse
prev parent reply other threads:[~2006-06-28 0:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-27 20:10 Jesse Brandeburg
2006-06-27 21:43 ` Sam Ravnborg
2006-06-28 0:25 ` Jesse Brandeburg [this message]
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=4807377b0606271725u678901a1h8d9d6776b82db3b4@mail.gmail.com \
--to=jesse.brandeburg@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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
all inboxes | Powered by JetHome®