From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Conflict between uClibc-ng if_arp.h and kernel headers since Linux 4.11 ?
Date: Thu, 4 May 2017 23:39:31 +0200 [thread overview]
Message-ID: <20170504233931.450f0a40@free-electrons.com> (raw)
Hello,
Since a few days, we are seeing build failures of the radvd package in
Buildroot:
http://autobuild.buildroot.net/?reason=radvd-2.12
The build failure is:
/home/buildroot/autobuild/run/instance-2/output/host/usr/arc-buildroot-linux-uclibc/sysroot/usr/include/linux/if_arp.h:121:8: error: redefinition of 'struct arpreq_old'
struct arpreq_old {
^~~~~~~~~~
In file included from includes.h:90:0,
from recv.c:17:
/home/buildroot/autobuild/run/instance-2/output/host/usr/arc-buildroot-linux-uclibc/sysroot/usr/include/net/if_arp.h:147:8: note: originally defined here
struct arpreq_old
^~~~~~~~~~
[...]
The build failures happens with uClibc-ng toolchains in combination
with Linux 4.11 kernel headers, so it seems to be a new thing caused by
Linux 4.11 headers. However the kernel Git history doesn't show any
change on this header file between 4.10 and 4.11.
Any idea?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next reply other threads:[~2017-05-04 21:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-04 21:39 Thomas Petazzoni [this message]
2017-05-09 9:13 ` [Buildroot] [uclibc-ng-devel] Conflict between uClibc-ng if_arp.h and kernel headers since Linux 4.11 ? Waldemar Brodkorb
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=20170504233931.450f0a40@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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