Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Thilo-Alexander Ginkel <thilo@ginkel.com>
To: wireguard@lists.zx2c4.com
Subject: Ubuntu 18.04 kernel 4.15.0-106-generic breaks wireguard-1.0.20200520
Date: Wed, 10 Jun 2020 12:41:24 +0200	[thread overview]
Message-ID: <CANvSZQ97BG02tHyTUBf46XUfJKXArx-gaKe-R2ao0UEUoh55LA@mail.gmail.com> (raw)

Hi there,

after updating to the current Ubuntu 18.04 kernel 4.15.0-106-generic
kernel wireguard-dkms no longer compiles with the following build
failure:

DKMS make.log for wireguard-1.0.20200520 for kernel 4.15.0-106-generic (x86_64)
Wed Jun 10 12:32:13 CEST 2020
make: Entering directory '/usr/src/linux-headers-4.15.0-106-generic'
  CC [M]  /var/lib/dkms/wireguard/1.0.20200520/build/main.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20200520/build/noise.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20200520/build/device.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20200520/build/peer.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20200520/build/timers.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20200520/build/queueing.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20200520/build/send.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20200520/build/receive.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20200520/build/socket.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20200520/build/peerlookup.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20200520/build/allowedips.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20200520/build/ratelimiter.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20200520/build/cookie.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20200520/build/netlink.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20200520/build/crypto/zinc/chacha20/chacha20.o
  PERLASM /var/lib/dkms/wireguard/1.0.20200520/build/crypto/zinc/chacha20/chacha20-x86_64.S
  CC [M]  /var/lib/dkms/wireguard/1.0.20200520/build/crypto/zinc/poly1305/poly1305.o
In file included from <command-line>:0:0:
/var/lib/dkms/wireguard/1.0.20200520/build/socket.c: In function ‘send6’:
/var/lib/dkms/wireguard/1.0.20200520/build/compat/compat.h:102:42:
error: ‘const struct ipv6_stub’ has no member named ‘ipv6_dst_lookup’;
did you mean ‘ipv6_dst_lookup_flow’?
 #define ipv6_dst_lookup_flow(a, b, c, d) ipv6_dst_lookup(a, b, &dst,
c) + (void *)0 ?: dst
                                          ^
/var/lib/dkms/wireguard/1.0.20200520/build/socket.c:139:20: note: in
expansion of macro ‘ipv6_dst_lookup_flow’
   dst = ipv6_stub->ipv6_dst_lookup_flow(sock_net(sock), sock, &fl,
                    ^~~~~~~~~~~~~~~~~~~~
scripts/Makefile.build:330: recipe for target
'/var/lib/dkms/wireguard/1.0.20200520/build/socket.o' failed
make[1]: *** [/var/lib/dkms/wireguard/1.0.20200520/build/socket.o] Error 1
make[1]: *** Waiting for unfinished jobs....
Makefile:1577: recipe for target
'_module_/var/lib/dkms/wireguard/1.0.20200520/build' failed
make: *** [_module_/var/lib/dkms/wireguard/1.0.20200520/build] Error 2
make: Leaving directory '/usr/src/linux-headers-4.15.0-106-generic'

Regards,
Thilo

             reply	other threads:[~2020-06-10 10:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-10 10:41 Thilo-Alexander Ginkel [this message]
2020-06-10 15:34 ` YU News
2020-06-11  8:29 ` Jason A. Donenfeld
2020-06-11 12:05   ` Thilo-Alexander Ginkel
2020-06-11 12:16 Martin Jurasik
2020-06-11 17:49 Ada Sauce
2020-06-11 18:41 ` Ada Sauce

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=CANvSZQ97BG02tHyTUBf46XUfJKXArx-gaKe-R2ao0UEUoh55LA@mail.gmail.com \
    --to=thilo@ginkel.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).