From: nicolas prochazka <prochazka.nicolas@gmail.com>
To: kexianbin@diyism.com
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: about wireguard-go
Date: Tue, 9 Oct 2018 11:24:31 +0200 [thread overview]
Message-ID: <CADdae-hGbeASZH3A+RWReEjT9oLYE50Oo4DRvtZSOjEept1nxQ@mail.gmail.com> (raw)
In-Reply-To: <CAKVinOWVa7YHMs_M=bmjJfE28Yh1Jr1Rtm7PCrdt9DOywoidhA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 794 bytes --]
thanks a lot
Regards
NIcolas Prochazka
Le mar. 9 oct. 2018 à 11:17, KeXianbin(http://diyism.com) <
kexianbin@diyism.com> a écrit :
> Some hint here:
> https://gist.github.com/diyism/60aa6ca24df772a4928f1aced65e72ee#file-bargeos-on-digitalocean-L40
>
> On Tue, Oct 9, 2018 at 5:14 PM, nicolas prochazka <
> prochazka.nicolas@gmail.com> wrote:
>
>> Hello,
>> We need to compile wireguard-go on linux, because we are using a closed
>> linux, under we cannot compile module,
>> how can we do ? make on wireguard-go tells us that is not recommend on
>> linux
>>
>> Regards,
>> Nicolas Prochazka
>>
>> _______________________________________________
>> WireGuard mailing list
>> WireGuard@lists.zx2c4.com
>> https://lists.zx2c4.com/mailman/listinfo/wireguard
>>
>>
>
[-- Attachment #1.2: Type: text/html, Size: 1773 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2018-10-09 9:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2018-10-09 9:27 ` nicolas prochazka
[not found] <mailman.1.1539079201.20756.wireguard@lists.zx2c4.com>
2018-10-09 10:23 ` Brian Candler
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=CADdae-hGbeASZH3A+RWReEjT9oLYE50Oo4DRvtZSOjEept1nxQ@mail.gmail.com \
--to=prochazka.nicolas@gmail.com \
--cc=kexianbin@diyism.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).