Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Martin Jurasik <martin.jurasik@gmx.de>
To: wireguard@lists.zx2c4.com
Subject: Aw: Re: Ubuntu 18.04 kernel 4.15.0-106-generic breaks wireguard-1.0.20200520
Date: Fri, 12 Jun 2020 20:22:26 +0200	[thread overview]
Message-ID: <trinity-bcc1ea44-937b-4b1f-a979-acf971aac3ac-1591986145982@3c-app-gmx-bs62> (raw)
In-Reply-To: <etPan.5ee21f64.7c09ac86.1105b@gmx.de>

I haven't seen any update of the wireguard package yet. Is it still missing?
 
I have only seen an update of wireguard-linux-compat but this isn't used under Ubuntu 18.04, right?
 
Thanks & Regards,
Martin
 
 
 

Gesendet: Donnerstag, 11. Juni 2020 um 14:11 Uhr
Von: "Martin Jurasik" <martin.jurasik@gmx.de>
An: wireguard@lists.zx2c4.com
Betreff: Re: Ubuntu 18.04 kernel 4.15.0-106-generic breaks wireguard-1.0.20200520

Hi Jason,
 
still no luck with the updated version. make still fails.
 
#####

wireguard/bionic,bionic,now 1.0.20200513-1~18.04 all [installed,automatic]
wireguard-dkms/bionic,bionic,now 1.0.20200611-0ppa1~18.04 all [installed]
wireguard-tools/bionic,now 1.0.20200513-1~18.04 amd64 [installed]
deploy@xxx:~$ sudo dpkg-reconfigure wireguard-dkms
 
------------------------------
Deleting module version: 1.0.20200611
completely from the DKMS tree.
------------------------------
Done.
Loading new wireguard-1.0.20200611 DKMS files...
Building for 4.15.0-101-generic 4.15.0-106-generic
Building initial module for 4.15.0-101-generic
ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/wireguard-dkms.0.crash'
Error! Bad return status for module build on kernel: 4.15.0-101-generic (x86_64)
Consult /var/lib/dkms/wireguard/1.0.20200611/build/make.log for more information.
 
deploy@xxx:~$ cat /var/lib/dkms/wireguard/1.0.20200611/build/make.log 
DKMS make.log for wireguard-1.0.20200611 for kernel 4.15.0-101-generic (x86_64)
Thu 11 Jun 14:07:36 CEST 2020
make: Entering directory '/usr/src/linux-headers-4.15.0-101-generic'
  CC [M]  /var/lib/dkms/wireguard/1.0.20200611/build/main.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20200611/build/noise.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20200611/build/device.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20200611/build/peer.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20200611/build/timers.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20200611/build/queueing.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20200611/build/send.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20200611/build/receive.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20200611/build/socket.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20200611/build/peerlookup.o
/var/lib/dkms/wireguard/1.0.20200611/build/socket.c: In function ‘send6’:
/var/lib/dkms/wireguard/1.0.20200611/build/socket.c:139:20: error: ‘const struct ipv6_stub’ has no member named ‘ipv6_dst_lookup_flow’; did you mean ‘ipv6_dst_lookup’?
   dst = ipv6_stub->ipv6_dst_lookup_flow(sock_net(sock), sock, &fl,
                    ^~~~~~~~~~~~~~~~~~~~
                    ipv6_dst_lookup
scripts/Makefile.build:330: recipe for target '/var/lib/dkms/wireguard/1.0.20200611/build/socket.o' failed
make[1]: *** [/var/lib/dkms/wireguard/1.0.20200611/build/socket.o] Error 1
make[1]: *** Waiting for unfinished jobs....
Makefile:1577: recipe for target '_module_/var/lib/dkms/wireguard/1.0.20200611/build' failed
make: *** [_module_/var/lib/dkms/wireguard/1.0.20200611/build] Error 2
make: Leaving directory '/usr/src/linux-headers-4.15.0-101-generic‘
 
##########

 
 Regards, 
Martin
 

       reply	other threads:[~2020-06-12 18:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <etPan.5ee21f64.7c09ac86.1105b@gmx.de>
2020-06-12 18:22 ` Martin Jurasik [this message]
2020-06-13  5:34   ` AW: " Joachim Lindenberg
2020-06-13  5:47   ` Jason A. Donenfeld
2020-06-13 15:34     ` Martin Jurasik

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=trinity-bcc1ea44-937b-4b1f-a979-acf971aac3ac-1591986145982@3c-app-gmx-bs62 \
    --to=martin.jurasik@gmx.de \
    --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).