From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2014-10-22
Date: Thu, 23 Oct 2014 18:02:53 +0200 [thread overview]
Message-ID: <544926AD.3070102@mind.be> (raw)
In-Reply-To: <20141023180141.2515ed1c@free-electrons.com>
On 23/10/14 18:01, Thomas Petazzoni wrote:
> 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?
Exactly.
If the patch is supposed to be upstreamable, it should probably add a
--enable-werror option like e.g. libcurl has.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2014-10-23 16:02 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
2014-10-23 16:02 ` Arnout Vandecappelle [this message]
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=544926AD.3070102@mind.be \
--to=arnout@mind.be \
--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