From: Bruno Wolff III <bruno@wolff.to>
To: wireguard@lists.zx2c4.com
Subject: d8738d57ab9ab976a1899e73d955d38317f44486 not building with 4.15.0-0.rc0.git6.
Date: Tue, 21 Nov 2017 13:41:37 -0600 [thread overview]
Message-ID: <20171121194137.GA20179@wolff.to> (raw)
I tried building the latest WireGuard on the latest rawhide kernel an got
the following error:
/home/bruno/WireGuard/src/netlink.c: In function ‘get_device_dump_real’:
/home/bruno/WireGuard/src/netlink.c:180:2: error: too many arguments to function ‘genl_dump_check_consistent’
genl_dump_check_consistent(cb, hdr, &genl_family);
^~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /home/bruno/WireGuard/src/netlink.c:11:0:
./include/net/genetlink.h:194:20: note: declared here
static inline void genl_dump_check_consistent(struct netlink_callback *cb,
^~~~~~~~~~~~~~~~~~~~~~~~~~
make[2]: *** [scripts/Makefile.build:306: /home/bruno/WireGuard/src/netlink.o] Error 1
I also got some warnings about redefining READ_ONCE:
CC [M] /home/bruno/WireGuard/src/netlink.o
In file included from ./include/linux/kernel.h:10:0,
from ./include/linux/skbuff.h:17,
from ./include/linux/ip.h:20,
from /home/bruno/WireGuard/src/compat/compat.h:528,
from <command-line>:0:
./include/linux/compiler.h:249:0: warning: "READ_ONCE" redefined
#define READ_ONCE(x) __READ_ONCE(x, 1)
In file included from <command-line>:0:0:
/home/bruno/WireGuard/src/compat/compat.h:42:0: note: this is the location of the previous definition
#define READ_ONCE ACCESS_ONCE
next reply other threads:[~2017-11-21 19:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-21 19:41 Bruno Wolff III [this message]
2017-11-21 19:51 ` Jason A. Donenfeld
2017-11-21 20:15 ` Bruno Wolff III
2017-11-26 12:45 ` Jason A. Donenfeld
2017-11-26 16:55 ` Bruno Wolff III
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=20171121194137.GA20179@wolff.to \
--to=bruno@wolff.to \
--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).