From: Brian Candler <b.candler@pobox.com>
To: wireguard@lists.zx2c4.com
Subject: Re: about wireguard-go
Date: Tue, 9 Oct 2018 11:23:18 +0100 [thread overview]
Message-ID: <15a2d91b-74e6-49f9-5ea8-f6f51294e4af@pobox.com> (raw)
In-Reply-To: <mailman.1.1539079201.20756.wireguard@lists.zx2c4.com>
[-- Attachment #1.1: Type: text/plain, Size: 1118 bytes --]
On 09/10/2018 11:00, wireguard-request@lists.zx2c4.com wrote:
> In fact :
>
> [nicolas@linux wireguard-go-0.0.20180613]$ printf 'package main\nconst
> UseTheKernelModuleInstead = 0xdeadbabe\n' > ireallywantobuildon_linux.go
> [nicolas@linux wireguard-go-0.0.20180613]$ make
> Makefile:7: *** Do not build this for Linux. Instead use the Linux kernel
> module. See wireguard.com/install/ for more info.. Stop.
Look in the Makefile
<https://github.com/WireGuard/wireguard-go/blob/master/Makefile>:
ifeq ($(shell go env GOOS),linux)
ifeq ($(wildcard .git),)
$(error Do not build this for Linux. Instead use the Linux kernel
module. See wireguard.com/install/ for more info.)
else
$(shell printf 'package main\nconst UseTheKernelModuleInstead =
0xdeadbabe\n' > ireallywantobuildon_linux.go)
endif
endif
Also see
https://www.gnu.org/software/make/manual/html_node/Wildcard-Function.html
It looks like you need to move the .git directory out of the way before
you build - or just modify the Makefile. And you shouldn't need to
manually create ireallywantobuildon_linux.go, because the Makefile does
it for you.
[-- Attachment #1.2: Type: text/html, Size: 1845 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next parent reply other threads:[~2018-10-09 10:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1.1539079201.20756.wireguard@lists.zx2c4.com>
2018-10-09 10:23 ` Brian Candler [this message]
2018-10-09 9:14 about wireguard-go nicolas prochazka
2018-10-09 9:17 ` KeXianbin(http://diyism.com)
2018-10-09 9:24 ` nicolas prochazka
2018-10-09 9:27 ` nicolas prochazka
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=15a2d91b-74e6-49f9-5ea8-f6f51294e4af@pobox.com \
--to=b.candler@pobox.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).