From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Bruno Wolff III <bruno@wolff.to>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Looks like 4.13 introduces a new incompatibility
Date: Mon, 10 Jul 2017 05:03:42 +0200 [thread overview]
Message-ID: <CAHmME9pbky9H=+QkXA2VMeZ3OQonxxZ_H2-Jiz8Gy6FeYuR+7g@mail.gmail.com> (raw)
In-Reply-To: <20170710025614.GA17552@wolff.to>
On Mon, Jul 10, 2017 at 4:56 AM, Bruno Wolff III <bruno@wolff.to> wrote:
> On Mon, Jul 10, 2017 at 04:01:04 +0200,
> "Jason A. Donenfeld" <Jason@zx2c4.com> wrote:
>>
>> Hey Bruno,
>>
>> Thanks for the heads up. Does this fix it?
>>
>>
>> https://git.zx2c4.com/WireGuard/commit/?id=3Ddd007ad550b3def8a858e57aa71=
8af9b00047a28
>
>
> It looks like it fixed the problem. (At least device.o gets built.) But i=
t
> seems there is another problem.
>
> [bruno@wolff src]$ make clean all
> make -C /lib/modules/4.13.0-0.rc0.git3.1.fc27.i686+PAE/build
> M=3D/home/bruno/WireGuard/src clean
> make[1]: Entering directory
> '/usr/src/kernels/4.13.0-0.rc0.git3.1.fc27.i686+PAE'
> CLEAN /home/bruno/WireGuard/src/.tmp_versions
> make[1]: Leaving directory
> '/usr/src/kernels/4.13.0-0.rc0.git3.1.fc27.i686+PAE'
> make -C tools clean
> make[1]: Entering directory '/home/bruno/WireGuard/src/tools'
> rm -f wg *.o *.d
> make[1]: Leaving directory '/home/bruno/WireGuard/src/tools'
> make -C /lib/modules/4.13.0-0.rc0.git3.1.fc27.i686+PAE/build
> M=3D/home/bruno/WireGuard/src modules
> make[1]: Entering directory
> '/usr/src/kernels/4.13.0-0.rc0.git3.1.fc27.i686+PAE'
> CC [M] /home/bruno/WireGuard/src/main.o
> CC [M] /home/bruno/WireGuard/src/noise.o
> CC [M] /home/bruno/WireGuard/src/device.o
> CC [M] /home/bruno/WireGuard/src/peer.o
> CC [M] /home/bruno/WireGuard/src/timers.o
> CC [M] /home/bruno/WireGuard/src/data.o
> CC [M] /home/bruno/WireGuard/src/send.o
> CC [M] /home/bruno/WireGuard/src/receive.o
> CC [M] /home/bruno/WireGuard/src/socket.o
> CC [M] /home/bruno/WireGuard/src/config.o
> CC [M] /home/bruno/WireGuard/src/hashtables.o
> CC [M] /home/bruno/WireGuard/src/routingtable.o
> CC [M] /home/bruno/WireGuard/src/ratelimiter.o
> CC [M] /home/bruno/WireGuard/src/cookie.o
> /home/bruno/WireGuard/src/cookie.c: In function =E2=80=98cookie_message_c=
reate=E2=80=99:
> /home/bruno/WireGuard/src/cookie.c:156:2: error: implicit declaration of
> function =E2=80=98get_random_bytes_wait=E2=80=99; did you mean =E2=80=98g=
et_random_bytes_arch=E2=80=99?
> [-Werror=3Dimplicit-function-declaration]
> get_random_bytes_wait(dst->nonce, COOKIE_NONCE_LEN);
> ^~~~~~~~~~~~~~~~~~~~~
> get_random_bytes_arch
> cc1: some warnings being treated as errors
> make[2]: *** [scripts/Makefile.build:303:
> /home/bruno/WireGuard/src/cookie.o] Error 1
I need to annoy Ted Tso about this. It'll get merged for rc1 or rc2.
Jason
next prev parent reply other threads:[~2017-07-10 2:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-10 1:48 Bruno Wolff III
2017-07-10 2:01 ` Jason A. Donenfeld
2017-07-10 2:56 ` Bruno Wolff III
2017-07-10 3:03 ` Jason A. Donenfeld [this message]
2017-07-10 3:17 ` Bruno Wolff III
2017-07-10 3:26 ` Jason A. Donenfeld
2017-07-10 5:44 ` Bruno Wolff III
2017-07-15 21:57 ` Bruno Wolff III
2017-07-15 22:22 ` 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='CAHmME9pbky9H=+QkXA2VMeZ3OQonxxZ_H2-Jiz8Gy6FeYuR+7g@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=bruno@wolff.to \
--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).