[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTimkngSrDFUcHOySkf22yY3Qr3p+m2qnwDzre+zk@mail.gmail.com>
Date: Fri, 6 Aug 2010 11:09:41 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Sam Ravnborg <sam@...nborg.org>
Cc: Michal Marek <mmarek@...e.cz>,
"Justin P. Mattock" <justinmattock@...il.com>, JBeulich@...ell.com,
aris@...hat.com, catalin.marinas@....com, jacmet@...site.dk,
lizf@...fujitsu.com, ulfalizer.lkml@...il.com,
zippel@...ux-m68k.org, linux-kbuild@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] kconfig: fix make oldconfig
On Fri, Aug 6, 2010 at 10:52 AM, Sam Ravnborg <sam@...nborg.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@...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