From: Silvan Nagl <mail@53c70r.de>
To: wireguard@lists.zx2c4.com
Subject: Re: dkms module build fails since at least 20191226 on CentOS
Date: Mon, 6 Jan 2020 21:48:57 +0100 [thread overview]
Message-ID: <fccf5fd0-4b23-1893-ea55-c49992fe3909@53c70r.de> (raw)
In-Reply-To: <c9aa2698-b245-31ef-3b47-956f2b9d2d52@53c70r.de>
Same problem persists under CentOS in newest version 0.0.20200105.
On 1/5/20 3:17 PM, Silvan Nagl wrote:
> Hi again,
>
> since the last WireGuard upgrade (wireguard-0.0.20191226) the dkms
> module does not build anymore. I just noticed that my CentOS box still
> runs on 0.0.20191206 so it appeared to work at firs glance but actually
> it just uses the old dkms module which was not overwritten by the new
> installation because it failed to build.
>
> Here is make all output:
>
> [root@static wireguard-0.0.20191226]# make all
> CC [M] /usr/src/wireguard-0.0.20191226/main.o
> CC [M] /usr/src/wireguard-0.0.20191226/noise.o
> CC [M] /usr/src/wireguard-0.0.20191226/device.o
> CC [M] /usr/src/wireguard-0.0.20191226/peer.o
> CC [M] /usr/src/wireguard-0.0.20191226/timers.o
> CC [M] /usr/src/wireguard-0.0.20191226/queueing.o
> CC [M] /usr/src/wireguard-0.0.20191226/send.o
> CC [M] /usr/src/wireguard-0.0.20191226/receive.o
> In file included from ./include/linux/init.h:5,
> from /usr/src/wireguard-0.0.20191226/compat/compat.h:50,
> from <command-line>:
> /usr/src/wireguard-0.0.20191226/receive.c: In function ‘wg_packet_receive’:
> /usr/src/wireguard-0.0.20191226/receive.c:578:17: error: implicit
> declaration of function ‘rng_is_initialized’; did you mean
> ‘zone_is_initialized’? [-Werror=implicit-function-declaration]
> unlikely(!rng_is_initialized())) {
> ^~~~~~~~~~~~~~~~~~
> ./include/linux/compiler.h:77:42: note: in definition of macro ‘unlikely’
> # define unlikely(x) __builtin_expect(!!(x), 0)
> ^
> cc1: some warnings being treated as errors
> make[2]: *** [scripts/Makefile.build:316:
> /usr/src/wireguard-0.0.20191226/receive.o] Error 1
> make[1]: *** [Makefile:1528: _module_/usr/src/wireguard-0.0.20191226]
> Error 2
> make: *** [Makefile:38: module] Error 2
>
> Greetings,
>
> Silvan
>
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2020-01-06 20:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-05 14:17 dkms module build fails since at least 20191226 on CentOS Silvan Nagl
2020-01-06 20:48 ` Silvan Nagl [this message]
2020-01-16 18:49 ` Jason A. Donenfeld
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=fccf5fd0-4b23-1893-ea55-c49992fe3909@53c70r.de \
--to=mail@53c70r.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).