public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Sam Ravnborg <sam@ravnborg.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kconfig update
Date: Sun, 9 Mar 2003 22:15:18 +0100	[thread overview]
Message-ID: <20030309211518.GA18087@mars.ravnborg.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0303092115310.32518-100000@serv>

On Sun, Mar 09, 2003 at 09:18:30PM +0100, Roman Zippel wrote:
> I still don't see what you mean. :)

Sample output:
$ make mrproper
$ make KBUILD_VERBOSE=0 defconfig
  HOSTCC  scripts/fixdep
  HOSTCC  scripts/split-include
.....
  HOSTLD  scripts/kconfig/conf
SAM> Until here, just normal build output
./scripts/kconfig/conf -d arch/i386/Kconfig
SAM> OK, we run conf
./arch/i386/defconfig:544: trying to assign nonexistent symbol NET_PCMCIA_RADIO
SAM> One warning, but not fatal so we proceed
*
* Linux Kernel Configuration
*
Support for paging of anonymous memory (SWAP) [Y/n/?] y

SAM> Snipped ~890 lines

Cryptographic API (CRYPTO) [N/y/?] n
*
* Library routines
*
CRC32 functions (CRC32) [N/m/y/?] n
$ _

So executing "make KBUILD_VERBOSE=0 defconfig"
results in ~930 lines of output, including one warning message.

What I request is that conf outputs essential stuff only, for example
warnings.
That would remove 900 lines of output when building a kernel,
and maybe people actually paid attention to the warnings generated
by kconfig.

In general I prefer minimum output when building the kernel, without
loosing the ability to follow progress.
One reason why we have some of the warnings left all around in the kernel is
due to the fact people does not see them when building their drivers etc.
With default options to make, warnings simply does not show up as visible,
and when the build proceeds the relevant parts scroll out.

See my point now?

Also speaking about warnings. How about sticking in a "warning:",
to make the format gcc compatible.
Something like attacted patch.

	Sam

===== scripts/kconfig/confdata.c 1.4 vs edited =====
--- 1.4/scripts/kconfig/confdata.c	Sun Dec  8 05:14:02 2002
+++ edited/scripts/kconfig/confdata.c	Sun Mar  9 22:11:37 2003
@@ -148,7 +148,7 @@
 				*p2 = 0;
 			sym = sym_find(line + 7);
 			if (!sym) {
-				fprintf(stderr, "%s:%d: trying to assign nonexistent symbol %s\n", name, lineno, line + 7);
+				fprintf(stderr, "%s:%d: warning: trying to assign nonexistent symbol %s\n", name, lineno, line + 7);
 				break;
 			}
 			switch (sym->type) {
@@ -181,7 +181,7 @@
 					memmove(p2, p2 + 1, strlen(p2));
 				}
 				if (!p2) {
-					fprintf(stderr, "%s:%d: invalid string found\n", name, lineno);
+					fprintf(stderr, "%s:%d: error: invalid string found\n", name, lineno);
 					exit(1);
 				}
 			case S_INT:
@@ -190,7 +190,7 @@
 					S_VAL(sym->def) = strdup(p);
 					sym->flags &= ~SYMBOL_NEW;
 				} else {
-					fprintf(stderr, "%s:%d: symbol value '%s' invalid for %s\n", name, lineno, p, sym->name);
+					fprintf(stderr, "%s:%d: error: symbol value '%s' invalid for %s\n", name, lineno, p, sym->name);
 					exit(1);
 				}
 				break;

  reply	other threads:[~2003-03-09 21:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-09  3:57 [PATCH] kconfig update Roman Zippel
2003-03-09  8:59 ` Christoph Hellwig
2003-03-09 12:14   ` Petr Baudis
2003-03-09 12:46 ` Roman Zippel
2003-03-09 19:01 ` Sam Ravnborg
2003-03-09 19:30   ` Roman Zippel
2003-03-09 19:34     ` Sam Ravnborg
2003-03-09 20:18       ` Roman Zippel
2003-03-09 21:15         ` Sam Ravnborg [this message]
2003-03-10 10:00           ` Roman Zippel
2003-03-10 19:12             ` Sam Ravnborg
     [not found] ` <20030314144329.GA2768@wanadoo.fr>
     [not found]   ` <Pine.LNX.4.44.0303141602330.5042-100000@serv>
2003-03-14 19:36     ` [PATCH] kconfig update, GTK+ updated Romain Lievin
  -- strict thread matches above, loose matches on Subject: below --
2003-05-28 22:59 [PATCH] kconfig update 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=20030309211518.GA18087@mars.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox