public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] -Werror unwanted?
Date: Mon, 14 May 2012 20:51:07 +0200	[thread overview]
Message-ID: <1337021467.19402.13.camel@belkin4> (raw)
In-Reply-To: <20120514202456.16b5beda@epia.jer-c2.orkz.net>

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

El lun, 14-05-2012 a las 20:24 +0200, Jeroen Roovers escribió:
> On Mon, 14 May 2012 18:01:22 +0200
> Chí-Thanh Christopher Nguyễn <chithanh@gentoo.org> wrote:
> 
> > -Werror is basically saying that it is not safe to ship code which
> > produces warnings.
> 
> An upstream demanding -Werror should work means upstream would need to
> test rather a lot more than their own favourite
> distro/architecture/library versions/kernel/userland, which isn't
> going to happen.
> 
> > I personally think that if an upstream says that no warnings must be
> > produced by the code, and a developer should look at them before
> > declaring any warnings safe, then that is best followed.
> 
> Upstream does not need to take into account warnings produced by
> compilers for lesser known architectures, as explained above.
> 
> As an upstream development aid to check code that has just been added
> or changed, -Werror is fine, but not in the wild jungle that is Gentoo.
> You might as well just look at the warnings themselves instead of
> breaking the build system by making them fatal. In other words, for
> upstream development it's convenient, but never for our users out there.
> 
> Also, bug reports based on *FLAGS=-Werror will be closed as INVALID.
> (Perhaps we should document that too.)
> 
> 
>      jer
> 
> 

I fully agree with Jeroen on this, -Werror problems should be reported
directly to upstream if people want to help them on fixing warnings.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2012-05-14 18:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-14 15:44 [gentoo-dev] -Werror unwanted? hasufell
2012-05-14 16:01 ` Chí-Thanh Christopher Nguyễn
2012-05-14 18:24   ` Jeroen Roovers
2012-05-14 18:51     ` Pacho Ramos [this message]
2012-05-14 20:42     ` Chí-Thanh Christopher Nguyễn
2012-05-14 23:52       ` [gentoo-dev] " Nikos Chantziaras
2012-05-14 16:10 ` [gentoo-dev] " Mike Frysinger
2012-05-14 16:13 ` Alexandre Rostovtsev
2012-05-14 17:03   ` hasufell
2012-05-14 18:58     ` Markos Chandras
2012-06-26  4:57       ` [gentoo-dev] " Ryan Hill
2012-06-26  4:59         ` Duncan
2012-06-26  8:23           ` hasufell
2012-06-26 10:49           ` Michał Górny
2012-05-14 18:37 ` [gentoo-dev] " Michał Górny
2012-05-15 11:29 ` Tony "Chainsaw" Vroon
2012-05-15 15:25   ` Kacper Kowalik
2012-05-15 16:37   ` Mike Frysinger

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=1337021467.19402.13.camel@belkin4 \
    --to=pacho@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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