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.20181007` Available
Date: Mon, 08 Oct 2018 11:59:55 +0000	[thread overview]
Message-ID: <AozBfUAj9R6CBOxNr3tbIBtvuptN8Mbtw2ataw0oMolR1d_6hCM_w1NYAUwvRs3c7k7jiOqQcG1S84tidhGtoj6QFz3BXbnHrcCXeNv8qGs=@protonmail.ch> (raw)
In-Reply-To: <CAHmME9qboTvSU1+bu8Oi-zwBp8f6UWnfaGb-NEtfsnvnJUL66w@mail.gmail.com>

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Monday, October 8, 2018 12:37 AM, Jason A. Donenfeld <Jason@zx2c4.com> wrote:

> On Sun, Oct 7, 2018 at 10:49 PM Jordan Glover
> Golden_Miller83@protonmail.ch wrote:
>
> > I got an error when doing in-tree build using WireGuard/contrib/kernel-tree/create-patch.sh
> > net/wireguard/receive.c:338:10: fatal error: selftest/counter.c: No such file or directory
> > #include "selftest/counter.c"
> > ^~~~~~~~~~~~~~~~~~~~
> > compilation terminated.
>
> Youch. I'm rewriting those scripts so that it picks up file name
> changes like this automatically, so it's not such a whack-a-mole
> situation.
>
> Let me know if this fixes it:
> https://git.zx2c4.com/WireGuard/commit/?id=28366408148d0f230daebd9a61c5f7bf0c3e0390
>
> Jason

Yes, this fixes this issue. Thank you.

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

      parent reply	other threads:[~2018-10-08 12:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-07 15:20 Jason A. Donenfeld
2018-10-07 20:49 ` Jordan Glover
2018-10-07 22:37   ` Jason A. Donenfeld
2018-10-07 22:43     ` logcabin
2018-10-07 22:50       ` Jason A. Donenfeld
2018-10-09 22:29         ` Sebastian Gottschall
2018-10-08 11:59     ` 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='AozBfUAj9R6CBOxNr3tbIBtvuptN8Mbtw2ataw0oMolR1d_6hCM_w1NYAUwvRs3c7k7jiOqQcG1S84tidhGtoj6QFz3BXbnHrcCXeNv8qGs=@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).