From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2014-10-22
Date: Thu, 23 Oct 2014 11:24:16 +0300 [thread overview]
Message-ID: <20141023082416.GG2220@tarshish> (raw)
In-Reply-To: <20141023063017.0B8391011FF@stock.ovh.net>
Hi Thomas, buildroot list,
On Thu, Oct 23, 2014 at 08:30:16AM +0200, Thomas Petazzoni wrote:
> arm | ipset-6.23 | NOK | http://autobuild.buildroot.net/results/2ae233d33b05fac10e9b6676a6ca179c75e4c1d9/
> mips64el | ipset-6.23 | NOK | http://autobuild.buildroot.net/results/4f55c2415281c6204500efe28fe9e24c8ef73863/
I started looking into these build failures and it makes me wonder. The direct
cause of these failures is a combination of two things. Host header directory,
/usr/local/include, being used for target build (clearly a bad thing), and
-Werror. We normally remove -Werror since it is quite useless when you only
want to build the package. The thing is that ipset add -Werror only when
configures with --enable-debug, which in turn is triggered by
BR2_ENABLE_DEBUG. This apparently causes other build issues as well
(http://patchwork.ozlabs.org/patch/400834/). Does it make sense to remove
-Werror in this case? This is after all what the user asks for when enabling
BR2_ENABLE_DEBUG. But then again, does it make sense to have the autobuilder
test BR2_ENABLE_DEBUG, given its relatively high rate of -Werror induced false
positives?
What do others think?
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2014-10-23 8:24 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 [this message]
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
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=20141023082416.GG2220@tarshish \
--to=baruch@tkos.co.il \
--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 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.