[Debian-med-packaging] Bug#976528: metabat: FTBFS on arm64: metabat2.h:264:2: error: impossible constraint in ‘asm’

[Lucas Nussbaum]

Source: metabat
Version: 2.15-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):
> /usr/bin/c++ -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fopenmp -Wl,-z,relro -Wl,-z,now  CMakeFiles/contigOverlaps.dir/contigOverlaps.cpp.o -o contigOverlaps  -lhts /usr/lib/aarch64-linux-gnu/libz.so /usr/lib/aarch64-linux-gnu/libboost_program_options.a /usr/lib/aarch64-linux-gnu/libboost_filesystem.a /usr/lib/aarch64-linux-gnu/libboost_system.a /usr/lib/aarch64-linux-gnu/libboost_graph.a /usr/lib/aarch64-linux-gnu/libboost_serialization.a /usr/lib/aarch64-linux-gnu/libboost_iostreams.a /usr/lib/aarch64-linux-gnu/libboost_regex.a 
> make[3]: Leaving directory '/<<PKGBUILDDIR>>/obj-aarch64-linux-gnu'
> [ 62%] Built target contigOverlaps
> In file included from /<<PKGBUILDDIR>>/src/metabat2.cpp:1:
> /<<PKGBUILDDIR>>/src/metabat2.h: In function ‘long long unsigned int rdtsc()’:
> /<<PKGBUILDDIR>>/src/metabat2.h:264:2: error: impossible constraint in ‘asm’
>   264 |  __asm__ __volatile__ ("rdtsc" : "=a" (lo), "=d" (hi));
>       |  ^~~~~~~
> make[3]: *** [src/CMakeFiles/metabat2.dir/build.make:85: src/CMakeFiles/metabat2.dir/metabat2.cpp.o] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/12/05/metabat_2.15-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.