From: Sam Cater <sam@samcater.com>
To: wireguard@lists.zx2c4.com
Subject: Cannot compile Noise.c on Kernel 5.0?
Date: Sun, 13 Jan 2019 22:26:35 +0000 [thread overview]
Message-ID: <e52ae637-f85b-139d-84c6-29de2db5383e@samcater.com> (raw)
Hi Wireguard Mailing List,
Probably going to be showing a lot of ignorance here!
Wireguard has run fine on this system in the past, but today I tried to
build 20181218 on self-built 5.0 kernel (which in and of itself seems
stable and working fine). The compile fails on src/noise.o with the
issue linked below on line 453.
If I switch back to the stock 4.19 kernel provided by Fedora then
everything compiles fine. It's also worth mentioning that the same issue
appears to happen when I install the COPR packages for Fedora.
Appreciate I'm a non-standard kernel but just in case it is a Linux 5
incompatibility rather than "I can't build software", I thought I'd post
here in case it was helpful.
Mini paste at: https://pastebin.com/raw/W4LRT5bx
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next reply other threads:[~2019-01-16 16:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-13 22:26 Sam Cater [this message]
2019-01-16 23:49 ` Jordan Glover
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=e52ae637-f85b-139d-84c6-29de2db5383e@samcater.com \
--to=sam@samcater.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).