All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Javier Martín" <lordhabbit@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [RFC] make output of compiling a bit less verbose to make warnings more visible
Date: Tue, 02 Sep 2008 19:30:27 +0200	[thread overview]
Message-ID: <1220376627.23879.32.camel@localhost> (raw)
In-Reply-To: <1220373834.6359.42.camel@fz.local>

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

El mar, 02-09-2008 a las 18:43 +0200, Felix Zielcke escribió:
> Hello,
> 
> I think it would be good if the output from compiling wouldn't be that
> verbose.
> Just like on compiling the Linux kernel.
> It shows only something like:
> 
> CC source.c
> LD built-in.o
> VDSO-SYM? bla
> 
> instead of that whole `gcc -D GRUB_UTIL -o xx x.c ...' thing.
> 
> I haven't bothered to check yet how complicated it would be to implement
> this but I think it would be better to ask first if you even like this
> idea :)
> 
This was discussed earlier; some people argued about warnings and such,
and the OP said this would make warnings stand out _more_, not less.
After some more posts that I don't really remember the discussion died.
the link to the full thread is at [0].

I tried to implement the proposal myself, but modifying the Ruby file
that creates the *.mk files from the *.rmk files proved to be a royal
PITA. I recall I proposed a switch over to a more common tool as Python
and... western-rolling-ball-crossing-the-street. Feel free to try!

-Habbit

[0] http://lists.gnu.org/archive/html/grub-devel/2008-06/msg00248.html

[-- Attachment #2: Esta parte del mensaje está firmada digitalmente --]
[-- Type: application/pgp-signature, Size: 827 bytes --]

  parent reply	other threads:[~2008-09-02 17:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-02 16:43 [RFC] make output of compiling a bit less verbose to make warnings more visible Felix Zielcke
2008-09-02 17:10 ` Felix Zielcke
2008-09-02 19:27   ` Robert Millan
2008-09-02 19:43     ` Vesa Jääskeläinen
2008-09-02 20:47       ` Colin D Bennett
2008-09-03  6:59         ` Felix Zielcke
2008-09-03  8:37           ` Bean
2008-09-03 10:37             ` Felix Zielcke
2008-09-02 17:30 ` Javier Martín [this message]
2008-09-03  7:05 ` Hans Lambermont

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=1220376627.23879.32.camel@localhost \
    --to=lordhabbit@gmail.com \
    --cc=grub-devel@gnu.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.