Closed 0xkag closed 3 years ago
A quick git blame shows changes in c0046fa6 and 27837300 on these lines made on 2021-01-19 by @gperciva.
Huh, that shouldn't be enabled unless your CPU supports AESNI. Could you please paste the contents of your cpusupport-config.h
? It should be in the main build directory (probably the top level of the source tree).
Never mind, I've reproduce it inside virtualbox. I'll have a fix soon.
Looks like a compiler thing:
_mm_loadu_si64
missing https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78782. It was added to master in 2019-03-08, for gcc-9._mm_loadu_si64
https://reviews.llvm.org/D21504. That was 2016-06-19.On my debian buster system, it works with clang-6 and clang-7 (the available version of clang), but not an version of gcc that's in the default package tree. So a temporary fix might be to try
CC=clang make
I'm working on a fix for old gcc.
Ah, on that note, for the curious: I can reproduce this on modern freebsd amd64, via
CC=gcc8 make
I believe that this was fixed in #474.
@0xkag Can you confirm that this is now working for you?
@gperciva, @cperciva, master
builds for me now:
% uname -a
Linux <redacted> 5.10.13-x86-linode161 #1 SMP Thu Feb 4 13:51:28 EST 2021 i686 GNU/Linux
% tarsnap --version
tarsnap 1.0.39-head
% git rev-parse HEAD
b27038c31906c0c8a7426d1a50d0d04e9342d929
Thanks, @0xkag!
Perhaps this is intentional? But in any case,
master
at d067c043d01e doesn't build on i686. It fails with the following error:I did not bother bisecting to determine when it was introduced.