From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Sam Ravnborg <sam@ravnborg.org>, Michal Marek <mmarek@suse.cz>,
JBeulich@novell.com, aris@redhat.com, catalin.marinas@arm.com,
jacmet@sunsite.dk, lizf@cn.fujitsu.com, ulfalizer.lkml@gmail.com,
zippel@linux-m68k.org, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kconfig: fix make oldconfig
Date: Fri, 06 Aug 2010 12:52:16 -0700 [thread overview]
Message-ID: <4C5C67F0.8070408@gmail.com> (raw)
In-Reply-To: <AANLkTimkngSrDFUcHOySkf22yY3Qr3p+m2qnwDzre+zk@mail.gmail.com>
On 08/06/2010 11:09 AM, Linus Torvalds wrote:
> On Fri, Aug 6, 2010 at 10:52 AM, Sam Ravnborg<sam@ravnborg.org> wrote:
>>
>> Hmm, I wonder why you call oldconfig explicitly?
>>
>> A plain "make -j16" executes "silentoldconfig" if there
>> is any changes in a Kconfig* file or in .config.
>> Just double checked and it works as I expected.
>>
>> So you are asked if there is any new options anyway even
>> if you skip your "oldconfig" step.
>
> Try this:
>
> git clean -dqfx
> make -j16> ../makes
>
> It doesn't work, because "make silentconfig" will say
>
> ***
> *** You have not yet configured your kernel!
> *** (missing kernel config file ".config")
> ***
> *** Please run some configurator (e.g. "make oldconfig" or
> *** "make menuconfig" or "make xconfig").
> ***
>
> which is why I always run "make oldconfig".
>
> Sure, I could do it only when I need to, but quite frankly, it's much
> easier to just always do the thing that works, rather than try
> something that doesn't work, do something else, and then re-try the
> thing that can fail.
>
> Linus
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
the above command does break over here. using the make oldconfig command
seems to be working after I did the make menuconfig.
Now before doing all of this I did make a copy of the entire kernel for
a new system Im building(clfs) so I went into that tree and did a make
oldconfig and(luckily) hit the non responsive oldconfig thing that Linus
had originally posted.
here is a strace of when make oldconfig was not working(with git log at
the top)
http://fpaste.org/317B/
and strace of a git pull today and make oldconfig does not crap out and
starts asking me y/n options:
http://fpaste.org/QWWn/
hope this helps with debugging and such.
Justin P. Mattock
next prev parent reply other threads:[~2010-08-06 19:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-04 12:51 [GIT] kbuild: kconfig changes Michal Marek
2010-08-05 23:33 ` Linus Torvalds
2010-08-06 1:27 ` Justin P. Mattock
2010-08-06 2:08 ` Linus Torvalds
2010-08-06 2:54 ` Justin P. Mattock
2010-08-06 5:13 ` [PATCH] kconfig: fix make oldconfig Sam Ravnborg
2010-08-06 6:02 ` Justin P. Mattock
2010-08-06 10:21 ` Michal Marek
2010-08-06 16:19 ` Linus Torvalds
2010-08-06 17:52 ` Sam Ravnborg
2010-08-06 18:09 ` Linus Torvalds
2010-08-06 19:52 ` Justin P. Mattock [this message]
2010-08-06 23:19 ` [GIT] kbuild: kconfig changes Arve Hjønnevåg
2010-08-07 4:01 ` Sam Ravnborg
2010-08-07 4:43 ` Arve Hjønnevåg
2010-08-08 15:57 ` Sam Ravnborg
2010-08-10 14:04 ` Michal Marek
2010-08-10 14:25 ` Sam Ravnborg
2010-08-11 19:51 ` Sam Ravnborg
2010-08-11 20:34 ` Sam Ravnborg
2010-08-11 23:39 ` Arve Hjønnevåg
2010-08-12 3:45 ` Sam Ravnborg
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=4C5C67F0.8070408@gmail.com \
--to=justinmattock@gmail.com \
--cc=JBeulich@novell.com \
--cc=aris@redhat.com \
--cc=catalin.marinas@arm.com \
--cc=jacmet@sunsite.dk \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=mmarek@suse.cz \
--cc=sam@ravnborg.org \
--cc=torvalds@linux-foundation.org \
--cc=ulfalizer.lkml@gmail.com \
--cc=zippel@linux-m68k.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