wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: "Steven Honson" <steven@honson.id.au>
To: "Bruno Wolff III" <bruno@wolff.to>, wireguard@lists.zx2c4.com
Subject: Re: Commit 4659d637e271d7f2814c6763035553331cca3a3f seems broken
Date: Sat, 31 Aug 2019 18:20:29 +1000	[thread overview]
Message-ID: <3661f1aa-d467-4e35-9b2c-9489730b3921@www.fastmail.com> (raw)
In-Reply-To: <20190831070855.GA20933@wolff.to>

Hi Bruno,

Thanks for reporting this. I just sent a patch through to the mailing list that should resolve this.

Cheers,
Steven

On Sat, 31 Aug 2019, at 5:08 PM, Bruno Wolff III wrote:
> I got builds error with 4659d637e271d7f2814c6763035553331cca3a3f, but not 
> with dcca03f27879701d7377109517176a3aae86619f.
> 
> [bruno@laptop2 src]$ make 
> KERNELDIR=/lib/modules/5.3.0-0.rc6.git2.2.fc32.x86_64/build clean all
>   CLEAN   /home/bruno/WireGuard/src
>   CLEAN   /home/bruno/WireGuard/src/Module.symvers
>   CLEAN   /home/bruno/WireGuard/src/tools/{wg,*.o,*.d}
>   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/queueing.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/peerlookup.o
>   CC [M]  /home/bruno/WireGuard/src/allowedips.o
>   CC [M]  /home/bruno/WireGuard/src/ratelimiter.o
>   CC [M]  /home/bruno/WireGuard/src/cookie.o
>   CC [M]  /home/bruno/WireGuard/src/netlink.o
>   CC [M]  /home/bruno/WireGuard/src/crypto/zinc/chacha20/chacha20.o
>   PERLASM 
> /home/bruno/WireGuard/src/crypto/zinc/chacha20/chacha20-x86_64.S
>   AS [M]  
> /home/bruno/WireGuard/src/crypto/zinc/chacha20/chacha20-x86_64.o
>   CC [M]  /home/bruno/WireGuard/src/crypto/zinc/poly1305/poly1305.o
>   PERLASM 
> /home/bruno/WireGuard/src/crypto/zinc/poly1305/poly1305-x86_64.S
>   AS [M]  
> /home/bruno/WireGuard/src/crypto/zinc/poly1305/poly1305-x86_64.o
>   CC [M]  /home/bruno/WireGuard/src/crypto/zinc/chacha20poly1305.o
>   CC [M]  /home/bruno/WireGuard/src/crypto/zinc/blake2s/blake2s.o
>   AS [M]  /home/bruno/WireGuard/src/crypto/zinc/blake2s/blake2s-x86_64.o
>   CC [M]  /home/bruno/WireGuard/src/crypto/zinc/curve25519/curve25519.o
>   LD [M]  /home/bruno/WireGuard/src/wireguard.o
>   Building modules, stage 2.
>   MODPOST 1 modules
>   CC      /home/bruno/WireGuard/src/wireguard.mod.o
>   LD [M]  /home/bruno/WireGuard/src/wireguard.ko
>   CC      /home/bruno/WireGuard/src/tools/wg.o
>   CC      /home/bruno/WireGuard/src/tools/config.o
>   CC      /home/bruno/WireGuard/src/tools/show.o
>   CC      /home/bruno/WireGuard/src/tools/mnlg.o
>   CC      /home/bruno/WireGuard/src/tools/terminal.o
>   CC      /home/bruno/WireGuard/src/tools/ipc.o
> ipc.c: In function ‘userspace_get_wireguard_interfaces’:
> ipc.c:189:8: warning: implicit declaration of function 
> ‘userspace_has_wireguard_interface’; did you mean 
> ‘userspace_get_wireguard_interfaces’? [-Wimplicit-function-declaration]
>   189 |   if (!userspace_has_wireguard_interface(ent->d_name))
>       |        ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>       |        userspace_get_wireguard_interfaces
> At top level:
> ipc.c:143:13: warning: ‘userspace_has_wireguard_iface’ defined but not 
> used [-Wunused-function]
>   143 | static bool userspace_has_wireguard_iface(const char *iface)
>       |             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>   CC      /home/bruno/WireGuard/src/tools/encoding.o
>   CC      /home/bruno/WireGuard/src/tools/curve25519.o
>   CC      /home/bruno/WireGuard/src/tools/setconf.o
>   CC      /home/bruno/WireGuard/src/tools/genkey.o
>   CC      /home/bruno/WireGuard/src/tools/showconf.o
>   CC      /home/bruno/WireGuard/src/tools/pubkey.o
>   CC      /home/bruno/WireGuard/src/tools/set.o
>   LD      /home/bruno/WireGuard/src/tools/wg
> /usr/bin/ld: ipc.o: in function `ipc_list_devices':
> ipc.c:(.text+0xf39): undefined reference to 
> `userspace_has_wireguard_interface'
> /usr/bin/ld: ipc.o: in function `ipc_get_device':
> ipc.c:(.text+0x109a): undefined reference to 
> `userspace_has_wireguard_interface'
> /usr/bin/ld: ipc.o: in function `ipc_set_device':
> ipc.c:(.text+0x1e64): undefined reference to 
> `userspace_has_wireguard_interface'
> collect2: error: ld returned 1 exit status
> make[1]: *** [<builtin>: wg] Error 1
> make: *** [Makefile:59: tools] Error 2
> 
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
>
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

      reply	other threads:[~2019-08-31  8:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-31  7:08 Commit 4659d637e271d7f2814c6763035553331cca3a3f seems broken Bruno Wolff III
2019-08-31  8:20 ` Steven Honson [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=3661f1aa-d467-4e35-9b2c-9489730b3921@www.fastmail.com \
    --to=steven@honson.id.au \
    --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).