From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2015-11-26
Date: Fri, 27 Nov 2015 14:03:09 +0100 [thread overview]
Message-ID: <1448629389.16816.4.camel@embedded.rocks> (raw)
In-Reply-To: <20151127073014.F0A24102391@stock.ovh.net>
On Fr, 2015-11-27 at 08:30 +0100, Thomas Petazzoni wrote:
> Build statistics for 2015-11-26
> ===============================
>
> Detail of failures
> ===================
>
> ?????????arm |????????????????arptables-0.0.4 | NOK | http://autobuil
> d.buildroot.net/results/b721e4fa24a0728c20fd2ec0663c2b5981387642/
I had a look at this. Build fails because of namespace collision
between netinet and linux headers, e.g IPPROTO_IP is both defined in
linux/in.h and?netinet/in.h.
Unfortunatly, I am not sure how to fix this properly.
Best regards
J?rg Krause
next prev parent reply other threads:[~2015-11-27 13:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-27 7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2015-11-26 Thomas Petazzoni
2015-11-27 8:57 ` Yann E. MORIN
2015-11-27 9:33 ` Yegor Yefremov
2015-11-27 15:21 ` Thomas Petazzoni
2015-11-27 13:03 ` Jörg Krause [this message]
2015-11-27 15:20 ` Thomas Petazzoni
2015-11-27 19:14 ` Jörg Krause
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=1448629389.16816.4.camel@embedded.rocks \
--to=joerg.krause@embedded.rocks \
--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