Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Daniel Rudd <danielrudd@startmail.com>
To: wireguard@lists.zx2c4.com
Subject: wireguard-dkms build fails with ubuntu 18.04
Date: Tue, 2 Jun 2020 19:44:43 +0100	[thread overview]
Message-ID: <3b276e57-18a1-cfad-ebb4-7bd167bbb97d@startmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 508 bytes --]

Hi

Non-technical user here so please forgive any errors on my part.

Wireguard-dkms build fails on Ubuntu 18.04 kernel 4.15.0-102-generic
(and previous) with error:

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-102-generic
(x86_64)
Consult /var/lib/dkms/wireguard/1.0.20200520/build/make.log for more
information.

Crash file attached.

Would be grateful if anyone could advise.

All the best

Daniel



[-- Attachment #2: dkms_make_log --]
[-- Type: text/plain, Size: 3011 bytes --]

ProblemType: Package
DKMSBuildLog:
 DKMS make.log for wireguard-1.0.20200520 for kernel 4.15.0-102-generic (x86_64)
 Fri 29 May 18:37:12 BST 2020
 make: Entering directory '/usr/src/linux-headers-4.15.0-102-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
 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,
                     ^~~~~~~~~~~~~~~~~~~~
   PERLASM /var/lib/dkms/wireguard/1.0.20200520/build/crypto/zinc/chacha20/chacha20-x86_64.S
 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....
 make[1]: *** wait: No child processes. Stop.
 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-102-generic'
DKMSKernelVersion: 4.15.0-102-generic
Date: Fri May 29 18:37:16 2020
DuplicateSignature: dkms:wireguard-dkms:1.0.20200520-0ppa1~18.04:/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’?
Package: wireguard-dkms 1.0.20200520-0ppa1~18.04
PackageVersion: 1.0.20200520-0ppa1~18.04
SourcePackage: wireguard-linux-compat
Title: wireguard-dkms 1.0.20200520-0ppa1~18.04: wireguard kernel module failed to build


                 reply	other threads:[~2020-06-17  7:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3b276e57-18a1-cfad-ebb4-7bd167bbb97d@startmail.com \
    --to=danielrudd@startmail.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).