From: Nicholas Kinar <n.kinar@usask.ca>
To: "wireguard@lists.zx2c4.com" <wireguard@lists.zx2c4.com>
Subject: Cannot build Wireguard for ARM embedded Linux 32-bit Tinkerboard
Date: Tue, 7 Jan 2020 23:57:18 +0000 [thread overview]
Message-ID: <94a4b886-b7f1-ec54-c5ff-d2447ca08d3a@usask.ca> (raw)
Hello,
I've attempted to build Wireguard on an Asus Tinkerboard S running
embedded Linux. The board was initially flashed with Tinker OS (Debian
Stretch), but I updated to the more recent version of Debian buster
using apt-get. This is a 32-bit processor.
Operating System: Debian GNU/Linux 10 (buster)
Kernel: Linux 4.4.132+
linaro@clavet-server:~$ uname -a
Linux clavet-server 4.4.132+ #1 SMP Wed Aug 21 19:15:55 CST 2019 armv7l
GNU/Linux
I've followed the installation and build instructions on the official
website. The kernel model does not install nor build due to a compiler
flag that is not supported. Apparently this flag is for a 64-bit
build. I've also tried to do installation using the git version and the
same build failure occurs. Here is the output of the make.log.
DKMS make.log for wireguard-0.0.20191219 for kernel 4.4.132+ (armv7l)
Tue Jan 7 22:24:08 UTC 2020
make: Entering directory '/usr/src/linux-headers-4.4.132+'
LD /var/lib/dkms/wireguard/0.0.20191219/build/built-in.o
CC [M] /var/lib/dkms/wireguard/0.0.20191219/build/main.o
CC [M] /var/lib/dkms/wireguard/0.0.20191219/build/noise.o
CC [M] /var/lib/dkms/wireguard/0.0.20191219/build/device.o
CC [M] /var/lib/dkms/wireguard/0.0.20191219/build/peer.o
gcc: error: unrecognized command line option ‘-mgeneral-regs-only’
gcc: error: unrecognized command line option ‘-mgeneral-regs-only’
gcc: error: unrecognized command line option ‘-mgeneral-regs-only’
make[1]: *** [scripts/Makefile.build:277:
/var/lib/dkms/wireguard/0.0.20191219/build/main.o] Error 1
make[1]: *** Waiting for unfinished jobs....
gcc: error: unrecognized command line option ‘-mgeneral-regs-only’
make[1]: *** [scripts/Makefile.build:277:
/var/lib/dkms/wireguard/0.0.20191219/build/noise.o] Error 1
make[1]: *** [scripts/Makefile.build:277:
/var/lib/dkms/wireguard/0.0.20191219/build/device.o] Error 1
make[1]: *** [scripts/Makefile.build:277:
/var/lib/dkms/wireguard/0.0.20191219/build/peer.o] Error 1
make: *** [Makefile:1471:
_module_/var/lib/dkms/wireguard/0.0.20191219/build] Error 2
make: Leaving directory '/usr/src/linux-headers-4.4.132+'
What do I have to do to compile Wireguard on this system? I've tried to
add various libraries (as per
https://devtalk.nvidia.com/default/topic/906942/jetson-tx1/failed-to-compile-kernel-module-gcc-cannot-recognize-aarch64-option-mgeneral-regs-only-/),
but the same problem occurs.
Wireguard works great on all of my 64-bit servers and it is being used
to create research networks. Thanks so much for creating this great tool.
Nicholas
--
Dr. Nicholas J. Kinar, PhD
Research Scientist | Global Water Futures
Assistant Director | Smart Water Systems Lab
University of Saskatchewan
306-966-2092 | n.kinar@usask.ca
http://www.usask.ca/hydrology
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next reply other threads:[~2020-01-09 6:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-07 23:57 Nicholas Kinar [this message]
2020-01-09 8:17 ` Cannot build Wireguard for ARM embedded Linux 32-bit Tinkerboard Ilie Halip
2020-01-09 21:20 ` Nicholas Kinar
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=94a4b886-b7f1-ec54-c5ff-d2447ca08d3a@usask.ca \
--to=n.kinar@usask.ca \
--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).