Github messages for voidlinux
 help / color / mirror / Atom feed
From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Wireguard dkms fails on latest 5.4(.28)
Date: Tue, 01 Feb 2022 17:59:48 +0100	[thread overview]
Message-ID: <20220201165948.SgnyP_eZpuhAC6FfAlwoqIy6MDUzmHUvXUrApLPAxcw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20558@inbox.vuxu.org>

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

Closed issue by emacsomancer on void-packages repository

https://github.com/void-linux/void-packages/issues/20558

Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System

* xuname:  
`Void 5.4.28_1 x86_64 GenuineIntel uptodate hold rrrmDFFFFFFFFFFFFF`

* package:  
  wireguard-dkms, linux5.4

### Expected behavior
Wireguard dkms builds.
### Actual behavior
Wireguard dkms fails to build for linux5.4.28
### Steps to reproduce the behavior
upgrade to latest 5.4 kernel

build log:
```
DKMS make.log for wireguard-1.0.20200330 for kernel 5.4.28_1 (x86_64)
Tue 31 Mar 2020 01:06:24 PM MDT
make: Entering directory '/usr/src/kernel-headers-5.4.28_1'
  AR      /var/lib/dkms/wireguard/1.0.20200330/build/built-in.a
  CC [M]  /var/lib/dkms/wireguard/1.0.20200330/build/main.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20200330/build/noise.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20200330/build/device.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20200330/build/peer.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20200330/build/timers.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20200330/build/queueing.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20200330/build/send.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20200330/build/receive.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20200330/build/socket.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20200330/build/peerlookup.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20200330/build/allowedips.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20200330/build/ratelimiter.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20200330/build/cookie.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20200330/build/netlink.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20200330/build/crypto/zinc/chacha20/chacha20.o
  PERLASM /var/lib/dkms/wireguard/1.0.20200330/build/crypto/zinc/chacha20/chacha20-x86_64.S
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
	LANGUAGE = (unset),
	LC_ALL = (unset),
	LC_CTYPE = "''",
	LC_COLLATE = "C",
	LC_NUMERIC = "C",
	LANG = "en_GB.UTF-8"
    are supported and installed on your system.
perl: warning: Falling back to a fallback locale ("en_GB.UTF-8").
  CC [M]  /var/lib/dkms/wireguard/1.0.20200330/build/crypto/zinc/poly1305/poly1305.o
  PERLASM /var/lib/dkms/wireguard/1.0.20200330/build/crypto/zinc/poly1305/poly1305-x86_64.S
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
	LANGUAGE = (unset),
	LC_ALL = (unset),
	LC_CTYPE = "''",
	LC_COLLATE = "C",
	LC_NUMERIC = "C",
	LANG = "en_GB.UTF-8"
    are supported and installed on your system.
perl: warning: Falling back to a fallback locale ("en_GB.UTF-8").
  CC [M]  /var/lib/dkms/wireguard/1.0.20200330/build/crypto/zinc/chacha20poly1305.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20200330/build/crypto/zinc/blake2s/blake2s.o
  AS [M]  /var/lib/dkms/wireguard/1.0.20200330/build/crypto/zinc/blake2s/blake2s-x86_64.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20200330/build/crypto/zinc/curve25519/curve25519.o
  AS [M]  /var/lib/dkms/wireguard/1.0.20200330/build/crypto/zinc/chacha20/chacha20-x86_64.o
  AS [M]  /var/lib/dkms/wireguard/1.0.20200330/build/crypto/zinc/poly1305/poly1305-x86_64.o
  LD [M]  /var/lib/dkms/wireguard/1.0.20200330/build/wireguard.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC [M]  /var/lib/dkms/wireguard/1.0.20200330/build/wireguard.mod.o
  LD [M]  /var/lib/dkms/wireguard/1.0.20200330/build/wireguard.ko
make: Leaving directory '/usr/src/kernel-headers-5.4.28_1'
```



  parent reply	other threads:[~2022-02-01 16:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-01 20:42 [ISSUE] " emacsomancer
2020-04-02  8:52 ` Piraty
2020-04-02  8:52 ` [ISSUE] [CLOSED] " Piraty
2022-02-01 14:45 ` michael-keyes
2022-02-01 16:59 ` paper42 [this message]
2022-02-01 16:59 ` paper42
2022-02-02 13:58 ` michael-keyes
2022-02-02 13:59 ` michael-keyes
2022-02-02 14:08 ` paper42
2022-02-02 14:24 ` michael-keyes
2022-02-02 14:33 ` paper42

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=20220201165948.SgnyP_eZpuhAC6FfAlwoqIy6MDUzmHUvXUrApLPAxcw@z \
    --to=paper42@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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 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).