From: Philipp Richter <richterphilipp.pops@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: Implicit declaration of function 'read_cpuid_part', asm/simd.h: No such file or directory with 0.0.20180925 on arm kernel 3.10.107
Date: Thu, 27 Sep 2018 08:54:15 +0200 [thread overview]
Message-ID: <CA+Vb7hpWG4DEfSFe_S1rajsuiVJkkfJ9Y29-tSWYnserOeGssQ@mail.gmail.com> (raw)
Hello,
it's me again with my super ancient kernel *sigh*
I'm getting these errors with the 0.0.20180925 snapshot :
DKMS make.log for wireguard-0.0.20180925 for kernel 3.10.107-2-ARCH (armv7l)
Thu Sep 27 08:44:18 CEST 2018
make: Entering directory '/usr/src/linux-3.10.107-2-ARCH'
LD /var/lib/dkms/wireguard/0.0.20180925/build/built-in.o
CC [M] /var/lib/dkms/wireguard/0.0.20180925/build/main.o
CC [M] /var/lib/dkms/wireguard/0.0.20180925/build/noise.o
CC [M] /var/lib/dkms/wireguard/0.0.20180925/build/device.o
CC [M] /var/lib/dkms/wireguard/0.0.20180925/build/peer.o
CC [M] /var/lib/dkms/wireguard/0.0.20180925/build/timers.o
CC [M] /var/lib/dkms/wireguard/0.0.20180925/build/queueing.o
CC [M] /var/lib/dkms/wireguard/0.0.20180925/build/send.o
CC [M] /var/lib/dkms/wireguard/0.0.20180925/build/receive.o
CC [M] /var/lib/dkms/wireguard/0.0.20180925/build/socket.o
CC [M] /var/lib/dkms/wireguard/0.0.20180925/build/hashtables.o
CC [M] /var/lib/dkms/wireguard/0.0.20180925/build/allowedips.o
CC [M] /var/lib/dkms/wireguard/0.0.20180925/build/ratelimiter.o
CC [M] /var/lib/dkms/wireguard/0.0.20180925/build/cookie.o
CC [M] /var/lib/dkms/wireguard/0.0.20180925/build/netlink.o
CC [M] /var/lib/dkms/wireguard/0.0.20180925/build/crypto/zinc/chacha20/chacha20.o
AS [M] /var/lib/dkms/wireguard/0.0.20180925/build/crypto/zinc/chacha20/chacha20-arm.o
CC [M] /var/lib/dkms/wireguard/0.0.20180925/build/crypto/zinc/poly1305/poly1305.o
AS [M] /var/lib/dkms/wireguard/0.0.20180925/build/crypto/zinc/poly1305/poly1305-arm.o
CC [M] /var/lib/dkms/wireguard/0.0.20180925/build/crypto/zinc/chacha20poly1305.o
CC [M] /var/lib/dkms/wireguard/0.0.20180925/build/crypto/zinc/blake2s/blake2s.o
In file included from
/var/lib/dkms/wireguard/0.0.20180925/build/crypto/zinc/chacha20/chacha20.c:20:
/var/lib/dkms/wireguard/0.0.20180925/build/crypto/zinc/chacha20/chacha20-arm-glue.h:
In function ‘chacha20_fpu_init’:
/var/lib/dkms/wireguard/0.0.20180925/build/crypto/zinc/chacha20/chacha20-arm-glue.h:30:10:
error: implicit declaration of function ‘read_cpuid_part’; did you
mean ‘read_cpuid_ext’? [-Werror=implicit-function-declaration]
switch (read_cpuid_part()) {
^~~~~~~~~~~~~~~
read_cpuid_ext
CC [M] /var/lib/dkms/wireguard/0.0.20180925/build/crypto/zinc/curve25519/curve25519.o
cc1: some warnings being treated as errors
make[1]: *** [scripts/Makefile.build:309:
/var/lib/dkms/wireguard/0.0.20180925/build/crypto/zinc/chacha20/chacha20.o]
Error 1
make[1]: *** Waiting for unfinished jobs....
In file included from
/var/lib/dkms/wireguard/0.0.20180925/build/crypto/zinc/curve25519/curve25519.c:25:
/var/lib/dkms/wireguard/0.0.20180925/build/crypto/zinc/curve25519/curve25519-arm-glue.h:8:10:
fatal error: asm/simd.h: No such file or directory
#include <asm/simd.h>
^~~~~~~~~~~~
compilation terminated.
make[1]: *** [scripts/Makefile.build:308:
/var/lib/dkms/wireguard/0.0.20180925/build/crypto/zinc/curve25519/curve25519.o]
Error 1
make: *** [Makefile:1233:
_module_/var/lib/dkms/wireguard/0.0.20180925/build] Error 2
make: Leaving directory '/usr/src/linux-3.10.107-2-ARCH'
I understand if it's just no possible anymore to support such ancient
software. Instead of collecting dust it serves as a nice wireguard
endpoint :)
Wireguard has been amazing so far, thanks for such great software.
Best Regards,
Philipp Richter
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next reply other threads:[~2018-10-02 3:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-27 6:54 Philipp Richter [this message]
2018-09-27 7:10 ` Philipp Richter
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=CA+Vb7hpWG4DEfSFe_S1rajsuiVJkkfJ9Y29-tSWYnserOeGssQ@mail.gmail.com \
--to=richterphilipp.pops@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).