[Debian-med-packaging] Bug#976527: bolt-lmm: FTBFS on arm64: MemoryUtils.hpp:34:10: fatal error: xmmintrin.h: No such file or directory

[Lucas Nussbaum]

Source: bolt-lmm
Version: 2.3.4+dfsg-2
Severity: important
Justification: FTBFS on arm64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201205 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on arm64.

Relevant part (hopefully):
> g++ -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -O2 -DMEASURE_DGEMM -DVERBOSE -Wall -fopenmp -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security  -o BoltParEstCV.o -c BoltParEstCV.cpp
> In file included from BoltParEstCV.cpp:29:
> MemoryUtils.hpp:34:10: fatal error: xmmintrin.h: No such file or directory
>    34 | #include <xmmintrin.h>
>       |          ^~~~~~~~~~~~~
> compilation terminated.
> make[2]: *** [Makefile:126: BoltParEstCV.o] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/12/05/bolt-lmm_2.3.4+dfsg-2_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with me
so that we can identify if something relevant changed in the meantime.

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.