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 20:14:39 +0100 [thread overview]
Message-ID: <1448651679.3542.9.camel@embedded.rocks> (raw)
In-Reply-To: <20151127162035.49cabe73@free-electrons.com>
On Fr, 2015-11-27 at 16:20 +0100, Thomas Petazzoni wrote:
> Dear J?rg Krause,
>
> On Fri, 27 Nov 2015 14:03:09 +0100, J?rg Krause wrote:
>
> > > ?????????arm |????????????????arptables-0.0.4 | NOK | http://auto
> > > buil
> > > 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.
>
> That's a typical case of issue exhibited by musl. You can probably
> just
> remove the <linux/in.h> include completely.
>
Unfortunatly it is not so easy: 'libarptc.h' includes 'netinit/in.h'
through the local header file 'libarptc/arpt_kernel_headers.h' directly
and indirectly, e.g. through 'netinet/ip.h'. On the other hand it
includes 'linux/in.h' indirectly through the system header file
'linux/netfilter_arp/arp_tables.h'. The declarations from
'linux/netfilter_arp/arp_tables.h' are required, so this header cannot
be removed easily.
Any idea?
Best regards
J?rg Krause
prev parent reply other threads:[~2015-11-27 19:14 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
2015-11-27 15:20 ` Thomas Petazzoni
2015-11-27 19:14 ` Jörg Krause [this message]
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=1448651679.3542.9.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