mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Paulo Andre'" <fscked@iol.pt>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.kernel.org
Subject: [RFC] [PATCH] Add 'make' with no target as preferred build command
Date: Mon, 26 May 2003 18:29:07 +0100	[thread overview]
Message-ID: <20030526182907.108fd71e.fscked@iol.pt> (raw)

[-- Attachment #1: Type: text/plain, Size: 435 bytes --]

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.

Applies on top of bk-curr. Please consider.


		Paulo Andre'



[-- Attachment #2: patch-scripts_kconfig_mconf.c.diff --]
[-- Type: text/plain, Size: 571 bytes --]

--- linux-2.5-vanilla/scripts/kconfig/mconf.c	2003-03-24 22:00:10.000000000 +0000
+++ linux-2.5/scripts/kconfig/mconf.c	2003-05-26 12:49:13.000000000 +0100
@@ -781,7 +781,7 @@
 		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");
+			"*** Next, you may run 'make', 'make bzImage', 'make bzdisk', or 'make install'.\n\n");
 	} else
 		printf("\n\nYour kernel configuration changes were NOT saved.\n\n");
 


             reply	other threads:[~2003-05-26 17:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-26 17:29 Paulo Andre' [this message]
2003-05-26 20:34 ` Sam Ravnborg
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=20030526182907.108fd71e.fscked@iol.pt \
    --to=fscked@iol.pt \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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®