From: Bruno Wolff III <bruno@wolff.to>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: wireguard@lists.zx2c4.com
Subject: Re: [WireGuard] wg doesn't build on 4.7 kernels
Date: Wed, 29 Jun 2016 15:59:39 -0500 [thread overview]
Message-ID: <20160629205939.GA19300@wolff.to> (raw)
In-Reply-To: <CAHmME9rSj3+4YB_x0HY26TvATSwL6+gNkjoH+SJCA6q3K-H63g@mail.gmail.com>
On Wed, Jun 29, 2016 at 22:48:26 +0200,
"Jason A. Donenfeld" <Jason@zx2c4.com> wrote:
>Fixed here:
>https://git.zx2c4.com/WireGuard/commit/?id=530ee2b2906af4d635d4d5bbabda5250b4a2b33e
That fixed the reported problem, but another 4.7 change is causing problems.
See: https://www.spinics.net/lists/kernel/msg2233003.html
These are the errors:
/home/bruno/WireGuard/src/crypto/chacha20poly1305.c: In function ‘chacha20poly1305_init’:
/home/bruno/WireGuard/src/crypto/chacha20poly1305.c:40:30: error: ‘cpu_has_xmm2’ undeclared (first use in this function)
chacha20poly1305_use_sse2 = cpu_has_xmm2;
^~~~~~~~~~~~
/home/bruno/WireGuard/src/crypto/chacha20poly1305.c:40:30: note: each undeclared identifier is reported only once for each function it appears in
/home/bruno/WireGuard/src/crypto/chacha20poly1305.c:42:30: error: ‘cpu_has_avx’ undeclared (first use in this function)
chacha20poly1305_use_avx2 = cpu_has_avx && cpu_has_avx2 &&
^~~~~~~~~~~
/home/bruno/WireGuard/src/crypto/chacha20poly1305.c:42:45: error: ‘cpu_has_avx2’ undeclared (first use in this function)
chacha20poly1305_use_avx2 = cpu_has_avx && cpu_has_avx2 &&
^~~~~~~~~~~~
scripts/Makefile.build:289: recipe for target '/home/bruno/WireGuard/src/crypto/chacha20poly1305.o' failed
make[2]: *** [/home/bruno/WireGuard/src/crypto/chacha20poly1305.o] Error 1
Makefile:1461: recipe for target '_module_/home/bruno/WireGuard/src' failed
make[1]: *** [_module_/home/bruno/WireGuard/src] Error 2
make[1]: Leaving directory '/usr/src/kernels/4.7.0-0.rc5.git1.2.fc25.x86_64'
Makefile:34: recipe for target 'module' failed
make: *** [module] Error 2
next prev parent reply other threads:[~2016-06-29 20:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-29 20:22 [WireGuard] wg doesn't build on 4.7 kernels Bruno Wolff III
2016-06-29 20:48 ` Jason A. Donenfeld
2016-06-29 20:59 ` Bruno Wolff III [this message]
2016-06-29 21:05 ` Jason A. Donenfeld
2016-06-29 21:06 ` Bruno Wolff III
2016-06-29 21:15 ` Jason A. Donenfeld
2016-06-29 21:19 ` Bruno Wolff III
2016-06-29 21:23 ` Jason A. Donenfeld
2016-06-30 0:06 ` Bruno Wolff III
2016-06-30 0:41 ` 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=20160629205939.GA19300@wolff.to \
--to=bruno@wolff.to \
--cc=Jason@zx2c4.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