From: Sam Ravnborg <sam@ravnborg.org>
To: "Paulo Andre'" <fscked@iol.pt>
Cc: Linus Torvalds <torvalds@transmeta.com>,
linux-kernel@vger.kernel.org,
Roman Zippel <zippel@linux-m68k.org>
Subject: Re: [RFC] [PATCH] Add 'make' with no target as preferred build command
Date: Mon, 26 May 2003 22:34:43 +0200 [thread overview]
Message-ID: <20030526203443.GA1209@mars.ravnborg.org> (raw)
In-Reply-To: <20030526182907.108fd71e.fscked@iol.pt>
On Mon, May 26, 2003 at 06:29:07PM +0100, Paulo Andre' wrote:
> Hello,
>
> It seems for 2.5/2.6 'make' is the preferred command for building the
> kernel tree (also stated in davej's 2.6 "what to expect" document). That
> scenario however isn't even presented when the user finishes the kernel
> configuration. This is a simple patch to scripts/kconfig/mconf.c which
> tackles that, perhaps not in the best fashion but certainly in the
> simplest.
If we really want this boilerplate text then bzImage should not be
present. It is i386 centric.
Revised patch below. Also made it a bit more readable by wrapping
a long line.
Roman Zippel cc:ed as he is the kconfig maintainer.
Sam
===== scripts/kconfig/mconf.c 1.5 vs edited =====
--- 1.5/scripts/kconfig/mconf.c Sat Mar 15 18:25:55 2003
+++ edited/scripts/kconfig/mconf.c Mon May 26 22:30:47 2003
@@ -780,10 +780,12 @@
conf_write(NULL);
printf("\n\n"
"*** End of Linux kernel configuration.\n"
- "*** Check the top-level Makefile for additional configuration.\n"
- "*** Next, you may run 'make bzImage', 'make bzdisk', or 'make install'.\n\n");
+ "*** Execute 'make' to build the kernel"
+ " or try 'make help'.\n\n");
} else
- printf("\n\nYour kernel configuration changes were NOT saved.\n\n");
+ printf("\n\n"
+ "*** Your kernel configuration changes were NOT saved."
+ "\n\n");
return 0;
}
next prev parent reply other threads:[~2003-05-26 20:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-26 17:29 [RFC] [PATCH] Add 'make' with no target as preferred build command Paulo Andre'
2003-05-26 20:34 ` Sam Ravnborg [this message]
2003-05-26 22:38 ` Paulo Andre'
2003-05-28 16:37 ` 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=20030526203443.GA1209@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=fscked@iol.pt \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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;
as well as URLs for NNTP newsgroup(s).