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: Mon, 15 May 2017 09:56:18 +0200 [thread overview]
Message-ID: <6c156160-706e-7f87-117e-5c2c9784ec6f@uclouvain.be> (raw)
In-Reply-To: <59185B16.5020107@iogearbox.net>
[-- Attachment #1.1: Type: text/plain, Size: 990 bytes --]
On 05/14/2017 03:26 PM, Daniel Borkmann wrote:
>
> David, are you still looking into fixing this?
Sorry, I left the issue on the side and then forgot about it.
Could you try the following iproute2 patch ? Thanks
diff --git a/include/linux/seg6.h b/include/linux/seg6.h
index 0715279..dd28017 100644
--- a/include/linux/seg6.h
+++ b/include/linux/seg6.h
@@ -15,7 +15,12 @@
#define _LINUX_SEG6_H
#include <linux/types.h>
+
+#ifdef __KERNEL__
#include <linux/in6.h> /* For struct in6_addr. */
+#else
+#include <netinet/in.h>
+#endif
/*
* SRH
diff --git a/ip/iproute_lwtunnel.c b/ip/iproute_lwtunnel.c
index 1395f03..434e60a 100644
--- a/ip/iproute_lwtunnel.c
+++ b/ip/iproute_lwtunnel.c
@@ -20,9 +20,6 @@
#include <linux/lwtunnel.h>
#include <linux/mpls_iptunnel.h>
-#ifndef __USE_KERNEL_IPV6_DEFS
-#define __USE_KERNEL_IPV6_DEFS
-#endif
#include <linux/seg6.h>
#include <linux/seg6_iptunnel.h>
#include <linux/seg6_hmac.h>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2017-05-15 7:55 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
2017-05-15 7:56 ` David Lebrun [this message]
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=6c156160-706e-7f87-117e-5c2c9784ec6f@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.