From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Kevin <anaknaga@inventati.org>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Trouble building WireGuard since December releases
Date: Mon, 22 Jan 2018 16:53:32 +0100 [thread overview]
Message-ID: <CAHmME9qY1rVUxsdkD+M91pZJNcncG+PrG-9ypK0YPvfb4k4_JA@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9rEFgWHewhf8mC=7ec=NRdhqAJQtuG1ggby-Bzfd8zaaw@mail.gmail.com>
Worked exactly as intended for me.
1. I downloaded the latest ISO from the solus website.
2. I installed it using the GUI installer.
3. I booted into the new installation.
4. I updated all packages using the GUI updater.
5. I ran these commands in the built-in terminal:
$ sudo eopkg install git
$ sudo eopkg install -c kernel.devel
$ sudo eopkg install -c system.devel
$ sudo eopkg install libmnl-devel
$ git clone https://git.zx2c4.com/WireGuard
$ cd WireGuard/src && make debug -j$(nproc) && sudo make install
$ sudo modprobe wireguard && dmesg | grep wireguard
[ 31.554056] wireguard: loading out-of-tree module taints kernel.
[ 31.555061] wireguard: allowedips self-tests: pass
[ 31.555463] wireguard: nonce counter self-tests: pass
[ 31.555761] wireguard: curve25519 self-tests: pass
[ 31.555798] wireguard: chacha20poly1305 self-tests: pass
[ 31.555808] wireguard: poly1305 self-tests: pass
[ 31.556129] wireguard: blake2s self-tests: pass
[ 31.755518] wireguard: ratelimiter self-tests: pass
[ 31.755531] wireguard: WireGuard 0.0.20180118-2-gc80cbfa loaded.
See www.wireguard.com for information.
[ 31.755532] wireguard: Copyright (C) 2015-2018 Jason A. Donenfeld
<Jason@zx2c4.com>. All Rights Reserved.
next prev parent reply other threads:[~2018-01-22 15:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 14:42 Kevin
2018-01-22 15:23 ` Greg KH
2018-01-22 15:34 ` Jason A. Donenfeld
2018-01-22 15:53 ` Jason A. Donenfeld [this message]
2018-01-22 16:07 ` Jason A. Donenfeld
2018-01-24 18:49 ` Daniel Kahn Gillmor
2018-01-24 23:07 ` 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=CAHmME9qY1rVUxsdkD+M91pZJNcncG+PrG-9ypK0YPvfb4k4_JA@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=anaknaga@inventati.org \
--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).