From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
Cc: Roman Zippel <zippel@linux-m68k.org>,
Sam Ravnborg <sam@ravnborg.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
kbuild-devel <kbuild-devel@lists.sourceforge.net>
Subject: Re: [kbuild-devel] linux kernel conf 0.6
Date: Sun, 22 Sep 2002 21:48:14 -0400 [thread overview]
Message-ID: <3D8E72DE.6020502@mandrakesoft.com> (raw)
In-Reply-To: Pine.LNX.4.44.0209221756130.11808-100000@chaos.physics.uiowa.edu
Kai Germaschewski wrote:
> On Sun, 22 Sep 2002, Jeff Garzik wrote:
> AFAICS, "quiet" only means the same thing as the traditional "make
> oldconfig", but suppressing questions where the answers are known. (Which
> I think is fine)
yeah, that's fine with me too
> I was just referring to the following, which really is not in the subtle
> change category:
>
> -------------------------------------------------------------
> [kai@zephyr linux-2.5.make]$ rm .config
> [kai@zephyr linux-2.5.make]$ make
> ***
> *** You have not yet configured your kernel!
> ***
> *** Please run some configurator (e.g. "make oldconfig" or
> *** "make menuconfig" or "make xconfig").
> ***
> make: *** [.config] Error 1
> -------------------------------------------------------------
>
> whereas lkc changes this to run (the quiet) make oldconfig automatically.
hmmmm, looks like something got broken somewhere, then.
The proper behavior for this example is
cp arch/$arch/defconfig .config
Do a 'make oldconfig' or 'make config' with no .config, in a 2.4 kernel.
Please fix... :/
> Same thing for
>
> -------------------------------------------------------------
> [kai@zephyr linux-2.5.make]$ cp ../config-2.5 .config
> [kai@zephyr linux-2.5.make]$ make
> make[1]: Entering directory
> `/home/kai/src/kernel/v2.5/linux-2.5.make/scripts'
> make[1]: Leaving directory
> `/home/kai/src/kernel/v2.5/linux-2.5.make/scripts'
> ***
> *** You changed .config w/o running make *config?
> *** Please run "make oldconfig"
> ***
> -------------------------------------------------------------
>
> Since people run automated builds, erroring out is IMHO preferable to
> dropping into interactive mode, which likely happens when you run make
> oldconfig.
agreed
Jeff
next prev parent reply other threads:[~2002-09-23 1:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-16 23:16 linux kernel conf 0.6 Roman Zippel
2002-09-20 5:10 ` [kbuild-devel] " Sam Ravnborg
2002-09-22 15:24 ` Roman Zippel
2002-09-22 22:36 ` Kai Germaschewski
2002-09-22 22:41 ` Jeff Garzik
2002-09-22 22:51 ` Kai Germaschewski
2002-09-22 22:53 ` Jeff Garzik
2002-09-22 23:03 ` Kai Germaschewski
2002-09-23 1:48 ` Jeff Garzik [this message]
2002-09-22 23:07 ` Roman Zippel
2002-09-22 23:19 ` Kai Germaschewski
2002-09-22 23:30 ` Roman Zippel
2002-09-23 1:50 ` Jeff Garzik
2002-09-23 19:59 ` Sam Ravnborg
2002-10-03 11:17 ` Roman Zippel
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=3D8E72DE.6020502@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=kai@tp1.ruhr-uni-bochum.de \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.