Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Michael Pro <michael.adm@gmail.com>
To: Ed Maste <emaste@freebsd.org>
Cc: "Jason A. Donenfeld" <Jason@zx2c4.com>,
	wireguard@lists.zx2c4.com, kevans@freebsd.org
Subject: Re: FreeBSD current socket-src changed. Wireguard not compiling.
Date: Thu, 1 Sep 2022 08:40:07 +0300	[thread overview]
Message-ID: <CAA+Mow5Pq7MBUCxvnTUsdnBhwduVh-VywFLoyTNy4G65XcAyvQ@mail.gmail.com> (raw)
In-Reply-To: <CAPyFy2DWRu+9ctBiLRpzYdzRj7+tBB_fa1RQM7kwJTz7tTtLvA@mail.gmail.com>

FreeBSD Current (14.0)
http://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/14.0/
sources from iso or github - no matther
Changes to src are made by commit e7d02be19d40063783d6b8f1ff2bc4c7170fd434
Author Gleb Smirnoff <glebius@FreeBSD.org> Wed, 17 Aug 2022 21:50:32
+0300 (11:50 -0700)

ср, 31 авг. 2022 г. в 21:18, Ed Maste <emaste@freebsd.org>:
>
> On Mon, 29 Aug 2022 at 12:18, Jason A. Donenfeld <Jason@zx2c4.com> wrote:
> > On Tue, Aug 23, 2022 at 12:26:21PM +0300, Michael Pro wrote:
> > > Tonight after updating kernel freebsd current I got coredump with
> > > wireguard enabled kernel module.
> > > ...
> > Thanks. Is there a __FreeBSD_version__ change that corresponds?
>
> It is not an exact match, but was bumped to 1400066 shortly after and
> should be a suitable value to check.

  reply	other threads:[~2022-09-01  5:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-23  9:26 Michael Pro
2022-08-29 16:16 ` Jason A. Donenfeld
2022-08-31 18:18   ` Ed Maste
2022-09-01  5:40     ` Michael Pro [this message]
2022-09-04 17:07     ` Jason A. Donenfeld
2022-09-04 17:20       ` Jason A. Donenfeld

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=CAA+Mow5Pq7MBUCxvnTUsdnBhwduVh-VywFLoyTNy4G65XcAyvQ@mail.gmail.com \
    --to=michael.adm@gmail.com \
    --cc=Jason@zx2c4.com \
    --cc=emaste@freebsd.org \
    --cc=kevans@freebsd.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).