All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Lebrun <david.lebrun@uclouvain.be>
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: <netdev@vger.kernel.org>, <stephen@networkplumber.org>
Subject: Re: iproute2 build error due to sr-ipv6 lwtunnel
Date: Thu, 4 May 2017 11:28:03 +0200	[thread overview]
Message-ID: <3c0c0584-338d-47d0-76d4-e4408decc2c1@uclouvain.be> (raw)
In-Reply-To: <590AF0C3.6070006@iogearbox.net>


[-- Attachment #1.1: Type: text/plain, Size: 868 bytes --]

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 ?

David


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2017-05-04  9:27 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 [this message]
2017-05-04  9:55   ` Daniel Borkmann
2017-05-14 13:26     ` Daniel Borkmann
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=3c0c0584-338d-47d0-76d4-e4408decc2c1@uclouvain.be \
    --to=david.lebrun@uclouvain.be \
    --cc=daniel@iogearbox.net \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.