All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] Build system improvement
Date: Wed, 22 Jul 2009 18:59:13 +0200	[thread overview]
Message-ID: <20090722165913.GA8706@thorin> (raw)
In-Reply-To: <1248279294.8929.7.camel@mj>

On Wed, Jul 22, 2009 at 12:14:54PM -0400, Pavel Roskin wrote:
> On Wed, 2009-07-22 at 14:41 +0200, Felix Zielcke wrote:
> 
> > > [0] http://lists.gnu.org/archive/html/grub-devel/2009-05/msg00009.html
> > 
> > So what's now with it?
> > Marco can you at least say something about it?
> > It would be very nice if the warnings would be more visible by default.
> > Probable we can't ever use -Werror because different compilers produce
> > different warnings etc.
> > For example gentoo's gcc with his trampoline patch.
> 
> I don't see any warnings in any configuration, unless more warning flags
> are added (e.g. -Wconversion, which is very noisy).
> 
> We can use -Werror by default, but make it very easy to disable.  For
> instance, we could have a configure option --disable-strict-warnings.
> 
> GRUB is a bootloader; we don't want anyone's system to become unbootable
> because something was miscompiled.  Requiring an extra step to disable
> warnings would tell users to be more careful.

I completely agree with this (both things).

Except, I'd call it --disable-werror, I think it's clearer (and I vaguely
recall other projects using this flag).

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."



      reply	other threads:[~2009-07-22 16:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-25  2:39 [PATCH] Build system improvement Javier Martín
2009-01-25 10:34 ` Vesa Jääskeläinen
2009-01-25 13:23   ` Javier Martín
2009-01-25 16:38     ` Colin D Bennett
2009-04-10 23:25 ` phcoder
2009-04-11 10:09   ` Yoshinori K. Okuji
2009-04-11 11:55     ` phcoder
2009-04-11 15:29     ` Colin D Bennett
2009-04-12 21:24       ` Pavel Roskin
2009-04-13  1:07         ` David Miller
2009-04-13  5:03           ` Pavel Roskin
2009-04-14 14:52             ` Yoshinori K. Okuji
2009-05-03  8:29     ` Felix Zielcke
2009-07-22 12:41       ` Felix Zielcke
2009-07-22 16:14         ` Pavel Roskin
2009-07-22 16:59           ` Robert Millan [this message]

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=20090722165913.GA8706@thorin \
    --to=rmh@aybabtu.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.