From: Jordan Glover <Golden_Miller83@protonmail.ch>
To: Sam Cater <sam@samcater.com>
Cc: "wireguard@lists.zx2c4.com" <wireguard@lists.zx2c4.com>
Subject: Re: Cannot compile Noise.c on Kernel 5.0?
Date: Wed, 16 Jan 2019 23:49:17 +0000 [thread overview]
Message-ID: <dfiSsHVIrz0EYyaiMf2E1C7ZIxe86o0Fm_KYt30d5ZZl0LRxz2JZv_-z-_Mid2AcQVSNxuC73wjBEvT4JbbxNl4vpkvCd681rU6nSsf7b0U=@protonmail.ch> (raw)
In-Reply-To: <e52ae637-f85b-139d-84c6-29de2db5383e@samcater.com>
On Wednesday, January 16, 2019 5:37 PM, Sam Cater <sam@samcater.com> wrote:
> 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
For Linux 5.0 you need to use wireguard snapshot from git:
https://git.zx2c4.com/WireGuard/log/
The error you posted was fixed by:
https://git.zx2c4.com/WireGuard/commit/?id=a56a0fee861d104b9bdb22847656fc40a9b13079
Later in build there will be another error fixed by:
https://git.zx2c4.com/WireGuard/commit/?id=eb8316abc24da2e38de65d88c519aa8dfd6227f4
Jordan
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
prev parent reply other threads:[~2019-01-16 23:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-13 22:26 Cannot compile Noise.c on Kernel 5.0? Sam Cater
2019-01-16 23:49 ` Jordan Glover [this message]
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='dfiSsHVIrz0EYyaiMf2E1C7ZIxe86o0Fm_KYt30d5ZZl0LRxz2JZv_-z-_Mid2AcQVSNxuC73wjBEvT4JbbxNl4vpkvCd681rU6nSsf7b0U=@protonmail.ch' \
--to=golden_miller83@protonmail.ch \
--cc=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).