From: Daniel Borkmann <daniel@iogearbox•net>
To: David Lebrun <david.lebrun@uclouvain•be>
Cc: netdev@vger•kernel.org, stephen@networkplumber•org
Subject: Re: iproute2 build error due to sr-ipv6 lwtunnel
Date: Sun, 14 May 2017 15:26:46 +0200 [thread overview]
Message-ID: <59185B16.5020107@iogearbox.net> (raw)
In-Reply-To: <590AFA8A.30602@iogearbox.net>
On 05/04/2017 11:55 AM, Daniel Borkmann wrote:
> On 05/04/2017 11:28 AM, David Lebrun wrote:
>> On 05/04/2017 11:13 AM, Daniel Borkmann wrote:
>>> Hi David,
>>>
>>> I'm getting the following build error from e8493916a8ed ("iproute:
>>> add support for SR-IPv6 lwtunnel encapsulation"). Reverting your
>>> commit makes iproute2 build again for me. Please take a look.
>>
>> Hi Daniel,
>>
>> This is because linux/seg6.h does an include of linux/in6.h (cf kernel
>> commit ea3ebc73b46fbdb049dafd47543bb22efaa09c8e "uapi: fix linux/seg6.h
>> and linux/seg6_iptunnel.h userspace compilation errors"), and iproute2's
>> include/utils.h requires the system /usr/include/resolv.h, which itself
>> includes /usr/include/netinet/in.h, re-defining struct in6_addr.
>>
>> However, netinet/in.h protects some struct definitions with #ifndef
>> __USE_KERNEL_IPV6_DEFS, which is explicitly defined in
>> iproute_lwtunnel.c, thus avoiding this specific issue.
>>
>> What is your glibc version ?
>
> Ok, I see, on one of my machines I have an old user space, but
> latest net/net-next kernel (+ installed kernel headers) and
> iproute2. glibc version there is 2.18.
David, are you still looking into fixing this?
next prev parent reply other threads:[~2017-05-14 13:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-04 9:13 iproute2 build error due to sr-ipv6 lwtunnel Daniel Borkmann
2017-05-04 9:28 ` David Lebrun
2017-05-04 9:55 ` Daniel Borkmann
2017-05-14 13:26 ` Daniel Borkmann [this message]
2017-05-15 7:56 ` David Lebrun
2017-05-15 8:46 ` Daniel Borkmann
2017-05-15 15:24 ` Stephen Hemminger
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=59185B16.5020107@iogearbox.net \
--to=daniel@iogearbox$(echo .)net \
--cc=david.lebrun@uclouvain$(echo .)be \
--cc=netdev@vger$(echo .)kernel.org \
--cc=stephen@networkplumber$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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