From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: "Anthony J. Bentley" <anthony@anjbe.name>
Cc: ports@openbsd.org, WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: WireGuard for OpenBSD
Date: Wed, 23 May 2018 14:28:13 +0200 [thread overview]
Message-ID: <CAHmME9rYhZZ7AgmssYPuyFgfw3OZcD741aALWoocK-4j-+TjXw@mail.gmail.com> (raw)
In-Reply-To: <49690.1527065737@cathet.us>
On Wed, May 23, 2018 at 10:55 AM, Anthony J. Bentley <anthony@anjbe.name> w=
rote:
> Attached is one. It will need to be updated to use the next tag once
> it's released.
Looks good to me. Indeed I don't like this manually carrying files
from the next release in ${FILES}, but that problem goes away entirely
when I do actually tag that next release.
I've also moved all the usages of install's -v switch in the Makefile
to be the first switch, so now you can simply run: sed -i 's/install
-v/install/g;s/@install/install/g' src/tools/Makefile
>
> Is there a way that I'm missing to display the actual compile commands
> during build, rather than the "CC blah.o" output?
Yes -- pass "V=3D1" in MAKE_FLAGS.
>
>> 2. wireguard-go
>> Runtime dependencies: none
>> Buildtime dependencies: gmake, go
>> Fixup: sed -i 's/ -v / /g' Makefile
>> Build: export GOPATH=3D$(pwd)/gopath; go get -d; gmake
>> Install: gmake PREFIX=3D/usr/local install
>> URL template: https://git.zx2c4.com/wireguard-go/snapshot/wireguard-go-V=
ERSIO
>> 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.
I simplified it quite a bit last night, so hopefully it's easier now:
Runtime dependencies: none
Buildtime dependencies: gmake, go
Fixup: sed -i 's/install -v/install/g;s/@install/install/g' Makefile
Build: gmake
Install: gmake PREFIX=3D/usr/local install
URL template: https://git.zx2c4.com/wireguard-go/snapshot/wireguard-go-VERS=
ION.tar.xz
The installer curl|sh disaster has also been updated: https://=D7=90.cc/IKu=
Bc62Z
prev parent reply other threads:[~2018-05-23 12:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 15:50 Jason A. Donenfeld
2018-05-23 8:55 ` Anthony J. Bentley
2018-05-23 12:28 ` Jason A. Donenfeld [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=CAHmME9rYhZZ7AgmssYPuyFgfw3OZcD741aALWoocK-4j-+TjXw@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=anthony@anjbe.name \
--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).