From: Peter Korsgaard <peter@korsgaard.com>
To: Outback Dingo <outbackdingo@gmail.com>
Cc: wireguard@lists.zx2c4.com
Subject: Re: wg on arm 32-bit
Date: Wed, 27 Dec 2017 23:24:57 +0100 [thread overview]
Message-ID: <87bmijq05i.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CAKYr3zwZC7QMyLZJT55MquxSOuJsvBO3JrNntFEp23egqJAeKw@mail.gmail.com> (Outback Dingo's message of "Wed, 27 Dec 2017 12:57:47 -0500")
>>>>> "Outback" == Outback Dingo <outbackdingo@gmail.com> writes:
> seems that wireguard is not capabl;e of building for 32bit arm?
It works fine in Buildroot.
> | DEBUG: Executing shell function do_compile
> | NOTE: make -j 8 -e MAKEFLAGS=
> | CC /home/dingo/yocto/build_bin/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/wireguard-tools/0.0.20171221-r0/WireGuard-0.0.20171221/src/tools/config.o
> | CC /home/dingo/yocto/build_bin/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/wireguard-tools/0.0.20171221-r0/WireGuard-0.0.20171221/src/tools/curve25519.o
> | CC /home/dingo/yocto/build_bin/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/wireguard-tools/0.0.20171221-r0/WireGuard-0.0.20171221/src/tools/mnlg.o
> | CC /home/dingo/yocto/build_bin/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/wireguard-tools/0.0.20171221-r0/WireGuard-0.0.20171221/src/tools/wg.o
> | CC /home/dingo/yocto/build_bin/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/wireguard-tools/0.0.20171221-r0/WireGuard-0.0.20171221/src/tools/ipc.o
> | CC /home/dingo/yocto/build_bin/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/wireguard-tools/0.0.20171221-r0/WireGuard-0.0.20171221/src/tools/encoding.o
> | CC /home/dingo/yocto/build_bin/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/wireguard-tools/0.0.20171221-r0/WireGuard-0.0.20171221/src/tools/show.o
> | CC /home/dingo/yocto/build_bin/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/wireguard-tools/0.0.20171221-r0/WireGuard-0.0.20171221/src/tools/terminal.o
> | In file included from encoding.h:11:0,
> | from encoding.c:9:
> | containers.h: In function 'free_wgdevice':
> | containers.h:87:2: error: 'for' loop initial declarations are only
> allowed in C99 or C11 mode
It looks like you are not passing -std=gnu11 to gcc. Can you build with
V=1 to see the exact command line?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2017-12-27 22:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-27 17:57 Outback Dingo
2017-12-27 22:24 ` Peter Korsgaard [this message]
2017-12-28 14:25 ` Outback Dingo
2017-12-30 15:12 ` Jason A. Donenfeld
2017-12-31 0:29 ` Daniel Kahn Gillmor
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=87bmijq05i.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=outbackdingo@gmail.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).