Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Jordan Glover <Golden_Miller83@protonmail.ch>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [ANNOUNCE] WireGuard Snapshot `0.0.20181119` Available
Date: Mon, 19 Nov 2018 20:56:51 +0000	[thread overview]
Message-ID: <eWVtNeoI7uCtRrv_h9amEYo3gqiIRS6Zc1TtaAJOfF3Bz6sgNSauZ5pcUqyHDOlv2j5krKlXyVbxkerb8SMp9BrKMAsS9UDCvb2rh51iLAs=@protonmail.ch> (raw)
In-Reply-To: <CAHmME9puWPwmOjRYcEmmFAf2KMM2KyDiV4EJPHRBBXkNSBrZqg@mail.gmail.com>

On Monday, November 19, 2018 8:02 PM, Jason A. Donenfeld <Jason@zx2c4.com> wrote:

> Hi Jordan,
> On Mon, Nov 19, 2018 at 7:04 PM Jordan Glover
> Golden_Miller83@protonmail.ch wrote:
>
> > It fails to build for me (doing in-kernel build with Linux 4.20rc3 and WireGuard/contrib/kernel-tree/create-patch.sh) with below message:
> > make[2]: *** No rule to make target 'net/wireguard/crypto/zinc/chacha20/chacha20-x86_64.o', needed by 'net/wireguard/built-in.a'. Stop.
> > There is also following warn when applying wireguard patch:
> > diff: /WireGuard/src/**/*.S_shipped: No such file or directory
>
> Ugh, sorry. This keeps happening: neglecting the jerry rig scripts,
> because they're not in src/. I need to either move those into src/ or
> add them to the CI so that this doesn't happen again.
>
> https://git.zx2c4.com/WireGuard/patch/?id=37466fb996ea174cddd3d836c2f49c53b10648ad
> should fix it.
>
> Jason

I can confirm that above fix works. Thank you.

Jordan
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

      reply	other threads:[~2018-11-19 20:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-19 17:27 Jason A. Donenfeld
2018-11-19 18:04 ` Jordan Glover
2018-11-19 19:02   ` Jason A. Donenfeld
2018-11-19 20:56     ` Jordan Glover [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='eWVtNeoI7uCtRrv_h9amEYo3gqiIRS6Zc1TtaAJOfF3Bz6sgNSauZ5pcUqyHDOlv2j5krKlXyVbxkerb8SMp9BrKMAsS9UDCvb2rh51iLAs=@protonmail.ch' \
    --to=golden_miller83@protonmail.ch \
    --cc=Jason@zx2c4.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).