From: Chi Wing Wong <hklbj@icloud.com>
To: wireguard@lists.zx2c4.com
Subject: Re: Error to compile Wireguard for SUSE LES 15 SP3
Date: Tue, 21 Sep 2021 12:16:39 +0100 [thread overview]
Message-ID: <A98A7E01-FC85-45C0-9ACD-A02A60866F65@icloud.com> (raw)
In-Reply-To: <204FE162-0DEE-47E2-B345-0DFB5FE20325@icloud.com>
> Hi,
>
> I am new to wireguard and tried to install via compiling the latest version (from git) of Wireguard-Linux-compat for my SUSE Linux Enterprise server 15 SP3. However, there are 2 errors prompted during compiling. I have checked the mail archive mentioned about similar issue. However, I could not find the mentioned patch to resolve the error. Could you share any reference for me to tackle it? Many Thanks.
>
>
> In file included from <command-line>:0:0:
> /home/optionmaker/wireguard-linux-compat/src/compat/compat.h:1036:20: error: redefinition of ‘skb_reset_redirect’
> static inline void skb_reset_redirect(struct sk_buff *skb)
> ^~~~~~~~~~~~~~~~~~
> In file included from /home/optionmaker/wireguard-linux-compat/src/compat/compat.h:870:0,
> from <command-line>:0:
> /usr/src/linux-5.3.18-59.19/include/linux/skbuff.h:4543:20: note: previous definition of ‘skb_reset_redirect’ was h
> ere
> static inline void skb_reset_redirect(struct sk_buff *skb)
> ^~~~~~~~~~~~~~~~~~
> In file included from /home/optionmaker/wireguard-linux-compat/src/compat/compat.h:870:0,
> from <command-line>:0:
> /usr/src/linux-5.3.18-59.19/include/linux/skbuff.h:4543:20: note: previous definition of ‘skb_reset_redirect’ was h
> ere
> static inline void skb_reset_redirect(struct sk_buff *skb)
>
>
>
> /home/optionmaker/wireguard-linux-compat/src/compat/compat.h: At top level:
> /home/optionmaker/wireguard-linux-compat/src/compat/compat.h:1065:22: error: static declaration of ‘ip_tunnel_parse
> _protocol’ follows non-static declaration
> static inline __be16 ip_tunnel_parse_protocol(const struct sk_buff *skb)
> ^~~~~~~~~~~~~~~~~~~~~~~~
> In file included from /usr/src/linux-5.3.18-59.19/include/net/gre.h:6:0,
> from /usr/src/linux-5.3.18-59.19/include/linux/netfilter/nf_conntrack_proto_gre.h:5,
> from /usr/src/linux-5.3.18-59.19/include/net/netfilter/nf_conntrack.h:23,
> from /home/optionmaker/wireguard-linux-compat/src/compat/compat.h:947,
> from <command-line>:0:
> /usr/src/linux-5.3.18-59.19/include/net/ip_tunnels.h:294:8: note: previous declaration of ‘ip_tunnel_parse_protocol
> ’ was here
> __be16 ip_tunnel_parse_protocol(const struct sk_buff *skb);
> ^~~~~~~~~~~~~~~~~~~~~~~~
> In file included from /usr/src/linux-5.3.18-59.19/include/net/gre.h:6:0,
> from /usr/src/linux-5.3.18-59.19/include/linux/netfilter/nf_conntrack_proto_gre.h:5,
> from /usr/src/linux-5.3.18-59.19/include/net/netfilter/nf_conntrack.h:23,
> from /home/optionmaker/wireguard-linux-compat/src/compat/compat.h:947,
> from <command-line>:0:
> /usr/src/linux-5.3.18-59.19/include/net/ip_tunnels.h:294:8: note: previous declaration of ‘ip_tunnel_parse_protocol
> ’ was here
> __be16 ip_tunnel_parse_protocol(const struct sk_buff *skb);
>
>
>
> In file included from <command-line>:0:0:
> /home/optionmaker/wireguard-linux-compat/src/compat/compat.h:1078:32: error: static declaration of ‘ip_tunnel_heade
> r_ops’ follows non-static declaration
> static const struct header_ops ip_tunnel_header_ops = { .parse_protocol = ip_tunnel_parse_protocol };
> ^~~~~~~~~~~~~~~~~~~~
> In file included from /usr/src/linux-5.3.18-59.19/include/net/gre.h:6:0,
> from /usr/src/linux-5.3.18-59.19/include/linux/netfilter/nf_conntrack_proto_gre.h:5,
> from /usr/src/linux-5.3.18-59.19/include/net/netfilter/nf_conntrack.h:23,
> from /home/optionmaker/wireguard-linux-compat/src/compat/compat.h:947,
> from <command-line>:0:
> /usr/src/linux-5.3.18-59.19/include/net/ip_tunnels.h:293:32: note: previous declaration of ‘ip_tunnel_header_ops’ w
> as here
> extern const struct header_ops ip_tunnel_header_ops;
>
>
> Regards,
> Wing
parent reply other threads:[~2021-09-22 4:17 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <204FE162-0DEE-47E2-B345-0DFB5FE20325@icloud.com>]
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=A98A7E01-FC85-45C0-9ACD-A02A60866F65@icloud.com \
--to=hklbj@icloud.com \
--cc=wireguard@lists.zx2c4.com \
/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;
as well as URLs for NNTP newsgroup(s).