From: Clemens Gruber <clemens.gruber@pqgruber.com>
To: ptxdist@pengutronix.de
Subject: [ptxdist] iproute2 build errors when updating to 4.6
Date: Sun, 22 May 2016 01:55:13 +0200 [thread overview]
Message-ID: <20160521235513.GA410@archie.localdomain> (raw)
Hi,
I need some features from the new iproute2 4.6, but there seem to be
some kernel header vs glibc header incompatibilities occuring when
building the new iproute2 4.6 for ptxdist.
Two examples of the numerous build errors on ptxdist 2016.04.0, a
toolchain with glibc 2.22 and kernel + kernel-headers version 4.6.
In file included from m_ipt.c:17:0:
../include/linux/if.h:106:19: error: redeclaration of enumerator 'IFF_UP'
#define IFF_UP IFF_UP
^
../include/linux/if.h:79:2: note: previous definition of 'IFF_UP' was here
IFF_UP = 1<<0, /* sysfs */
^~~~~~
In file included from ../include/xtables.h:16:0,
from ../include/iptables.h:5,
from m_ipt.c:18:
TOOLCHAIN/sysroot-arm-v7a-linux-gnueabihf/usr/include/net/if.h:111:8: error: redefinition of 'struct ifmap'
struct ifmap
^~~~~
In file included from m_ipt.c:17:0:
../include/linux/if.h:189:8: note: originally defined here
struct ifmap {
^~~~~
There is a commit in version 4.6 of iproute2, which should already have fixed
these build errors:
http://git.kernel.org/cgit/linux/kernel/git/shemminger/iproute2.git/commit/?id=8a781d7e2580e14f097b23a7c4731bafc800a824
But somehow the problems still occur on ptxdist.
Any ideas what's going on?
Would be great to have the new iproute2 4.6 working in the next ptxdist release :)
Thanks,
Clemens
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2016-05-21 23:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-21 23:55 Clemens Gruber [this message]
2016-05-24 7:20 ` Alexander Aring
2016-05-24 7:30 ` Alexander Aring
2016-05-24 13:01 ` Clemens Gruber
2016-05-24 15:24 ` Alexander Aring
2016-05-24 18:08 ` Alexander Aring
2016-05-25 17:42 ` Clemens Gruber
2016-05-29 18:31 ` Alexander Aring
2016-05-30 19:59 ` Clemens Gruber
2016-06-15 18:37 ` Alexander Aring
2016-06-16 16:19 ` Clemens Gruber
2016-05-24 10:04 ` Michael Olbrich
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=20160521235513.GA410@archie.localdomain \
--to=clemens.gruber@pqgruber.com \
--cc=ptxdist@pengutronix.de \
/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