From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2016-05-23
Date: Tue, 24 May 2016 14:36:30 +0100 [thread overview]
Message-ID: <574458DE.4040302@imgtec.com> (raw)
In-Reply-To: <20160524063023.4C8B610173F@stock.ovh.net>
Hello everyone,
On 24/05/16 07:30, Thomas Petazzoni wrote:
> ===================
>
> arm | collectd-5.5.1 | NOK | http://autobuild.buildroot.net/results/24a35b63921cb9d747052f3bbfc3549ed20e18d7/
> mips64el | collectd-5.5.1 | NOK | http://autobuild.buildroot.net/results/af1eec00e472349c7dca76dcc8dd5cd37d82f5c3/
> nios2 | connman-1.32 | NOK | http://autobuild.buildroot.net/results/af3743bc0840cecf13664c081d6d205e5a8c9eca/
> mips64el | connman-1.32 | NOK | http://autobuild.buildroot.net/results/6593e1ca94f98e3c2a5fd90401f709cf2f7b1743/
> arm | connman-1.32 | NOK | http://autobuild.buildroot.net/results/5937a416c1f320a581b54a7bc61cbb69075e9e43/
> mipsel | connman-1.32 | NOK | http://autobuild.buildroot.net/results/5ff215f7c91411fef335890d8a86a3482dfdac3b/
I've been looking at these ones and they fail due to some changes made
in the Linux kernel that causes conflicts between Linux's linux/if.h and
glibc's net/if.h.
The failure looks like this in collectd's config.log:
linux/if.h:71:2: error: redeclaration of enumerator 'IFF_UP'
IFF_UP = 1<<0, /* sysfs */
net/if.h:44:5: note: previous definition of 'IFF_UP' was here
IFF_UP = 0x1, /* Interface is up. */
And like this on conman:
linux/if.h:86:2: error: redeclaration of enumerator 'IFF_DYNAMIC'
IFF_DYNAMIC = 1<<15, /* sysfs */
net/if.h:79:5: note: previous definition of 'IFF_DYNAMIC' was here
IFF_DYNAMIC = 0x8000 /* Dialup device with changing addresses. */
This problem has been already fixed upstream:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4a91cb61bb995e5571098188092e296192309c77
Anyone has an idea how to workaround this downstream?
Regards,
Vincent.
next prev parent reply other threads:[~2016-05-24 13:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2016-05-23 Thomas Petazzoni
2016-05-24 13:36 ` Vicente Olivert Riera [this message]
2016-05-24 13:39 ` Gustavo Zacarias
2016-05-24 13:44 ` Vicente Olivert Riera
2016-05-24 14:58 ` Thomas Petazzoni
2016-05-24 20:48 ` [Buildroot] Analysis of build " Thomas Petazzoni
2016-05-24 21:01 ` Bernd Kuhls
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=574458DE.4040302@imgtec.com \
--to=vincent.riera@imgtec.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