From: "Anthony J. Bentley" <anthony@anjbe.name>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: ports@openbsd.org, WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: WireGuard for OpenBSD
Date: Wed, 23 May 2018 02:55:37 -0600 [thread overview]
Message-ID: <49690.1527065737@cathet.us> (raw)
In-Reply-To: <CAHmME9pWK75RZAvTzMigCBH31g_ftr3d5c6yAsLTs-7nZyLCYg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1035 bytes --]
Jason A. Donenfeld writes:
> 1. wireguard-tools, providing wg(8) and wg-quick(8)
> Runtime dependencies: bash, wireguard-go, libc
> Buildtime dependencies: gmake, c compiler, libc
> Fixup: sed -i 's/ -v / /g' src/tools/Makefile
> Build: gmake -C src/tools WITH_WGQUICK=yes
> Install: gmake -C src/tools PREFIX=/usr/local install
> URL template: https://git.zx2c4.com/WireGuard/snapshot/WireGuard-VERSION.tar.
> xz
Attached is one. It will need to be updated to use the next tag once
it's released.
Is there a way that I'm missing to display the actual compile commands
during build, rather than the "CC blah.o" output?
> 2. wireguard-go
> Runtime dependencies: none
> Buildtime dependencies: gmake, go
> Fixup: sed -i 's/ -v / /g' Makefile
> Build: export GOPATH=$(pwd)/gopath; go get -d; gmake
> Install: gmake PREFIX=/usr/local install
> URL template: https://git.zx2c4.com/wireguard-go/snapshot/wireguard-go-VERSIO
> N.tar.xz
I don't know anything about Go ports, so my attempt at this didn't get
very far and hasn't built yet.
[-- Attachment #2: wireguard-tools.tar.gz --]
[-- Type: application/x-gzip, Size: 6010 bytes --]
next prev parent reply other threads:[~2018-05-23 8:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 15:50 WireGuard for OpenBSD Jason A. Donenfeld
2018-05-23 8:55 ` Anthony J. Bentley [this message]
2018-05-23 12:28 ` 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=49690.1527065737@cathet.us \
--to=anthony@anjbe.name \
--cc=Jason@zx2c4.com \
--cc=ports@openbsd.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).