Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2014-10-22
Date: Thu, 23 Oct 2014 18:01:41 +0200	[thread overview]
Message-ID: <20141023180141.2515ed1c@free-electrons.com> (raw)
In-Reply-To: <54491A5C.6030802@mind.be>

Dear Arnout Vandecappelle,

On Thu, 23 Oct 2014 17:10:20 +0200, Arnout Vandecappelle wrote:

> > That is indeed a very good question. In some sense, having -Werror
> > enabled when --enable-debug is passed is quite legitimate.
> 
>  No, I disagree with that. --enable-debug should be an option to enable anything
> that makes runtime debugging easier - sometimes it enables extra debugging
> output for instance.  -Werror is something which is only really valid for
> continuous integration.

So in other words, your suggestion is to patch the package so that it
does *not* use -Werror even when --enable-debug is used, correct?

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2014-10-23 16:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-23  6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-10-22 Thomas Petazzoni
2014-10-23  8:24 ` Baruch Siach
2014-10-23 12:01   ` Thomas Petazzoni
2014-10-23 15:10     ` Arnout Vandecappelle
2014-10-23 16:01       ` Thomas Petazzoni [this message]
2014-10-23 16:02         ` Arnout Vandecappelle
2014-10-23 12:08 ` Fabio Porcedda
2014-10-23 18:58   ` François Perrad
2014-10-24 15:01     ` Fabio Porcedda

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=20141023180141.2515ed1c@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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