All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Reinauer <stepan@coresystems.de>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] Tidy up 'make' output
Date: Wed, 18 Jun 2008 00:22:43 +0200	[thread overview]
Message-ID: <48583933.4080208@coresystems.de> (raw)
In-Reply-To: <20080617203710.GA31785@thorin>

Robert Millan wrote:
> On Tue, Jun 17, 2008 at 10:44:48AM -0700, Colin D Bennett wrote:
>   
>> with output that, in my opinion, makes it easier to see warnings and
>> errors:
>>
>>   COMPILE         ../util/getroot.c
>>   COMPILE         ../kern/device.c
>>   ../kern/device.c: In function 'grub_device_iterate':
>>   ../kern/device.c:84: warning: generating trampoline in object
>>   (requires executable stack)
>>   ../kern/device.c:84: warning: generating trampoline in object
>>   (requires executable stack)
>>   COMPILE         ../kern/disk.c 
>>   COMPILE         ../kern/err.c
>>   COMPILE         ../kern/misc.c
>>     
>
> I don't like the idea of hiding information this way.  If the goal is to
> catch warnings, I think -Werror can do a much better job (and catching
> errors shouldn't be a problem unless you're using make -j or -k).
>   
I would not consider this "hiding information". The information you see
(CFLAGS for example) don't really change across the lines and there's
always the chance to say V=1 to see all the compiler lines. The
opposite: The current forest of duplicate information is really what is
hiding the relevant information between a lot of uninteresting fuzz.
Maybe, you guys would prefer to set V=1 as the default, so one would
have to say V=0 to get above output? I am currently only compiling grub
with make -s, because that is the only way to get any decently parsable
output for finding issues in the code.

Please, please, don't use -Werror.  GRUB2 is currently hard enough to
build and the build system is less than optimal and elegant. While I
agree that clean code never throughs warnings, the amazing number of
different gccs and build environments out there would make developing
for grub2 and compiling it very hard. There are quite a number of
warnings that do not matter because the developers simply know better
than the compiler. -Werror will lead to ugly workarounds to suppress
these warnings and make adoption of new tool chain versions a task from
hell.

Stefan

-- 
coresystems GmbH • Brahmsstr. 16 • D-79104 Freiburg i. Br.
      Tel.: +49 761 7668825 • Fax: +49 761 7664613
Email: info@coresystems.de  • http://www.coresystems.de/
Registergericht: Amtsgericht Freiburg • HRB 7656
Geschäftsführer: Stefan Reinauer • Ust-IdNr.: DE245674866




  parent reply	other threads:[~2008-06-17 22:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-17 17:44 [PATCH] Tidy up 'make' output Colin D Bennett
2008-06-17 19:57 ` Pavel Roskin
2008-06-17 20:07   ` Colin D Bennett
2008-06-17 20:25     ` Pavel Roskin
2008-06-17 20:37 ` Robert Millan
2008-06-17 20:53   ` Pavel Roskin
2008-06-17 22:22   ` Stefan Reinauer [this message]
2008-06-18 17:43     ` Robert Millan
2008-06-17 22:31   ` Colin D Bennett
2008-06-18 17:46     ` Robert Millan
2008-06-18 18:02       ` Pavel Roskin
2008-06-18 22:21         ` Robert Millan

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=48583933.4080208@coresystems.de \
    --to=stepan@coresystems.de \
    --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.