[Aptitude-devel] Bug#978171: aptitude: FTBFS: pkgcachegen.h:32:10: fatal error: xxhash.h: No such file or directory

[Lucas Nussbaum]

Source: aptitude
Version: 0.8.13-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> g++ -DLOCALEDIR=\"/usr/share/locale\" -DHAVE_CONFIG_H -I. -I../../../../src/generic/apt -I../../..  -I../../.. -I../../../../src/generic/apt -I../../../.. -I../../../../src -I/usr/include -Wdate-time -D_FORTIFY_SOURCE=2 -DHELPDIR=\"/usr/share/aptitude\" -DPKGDATADIR=\"/usr/share/aptitude\"  -I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include -I/usr/include/cwidget -I/usr/lib/x86_64-linux-gnu/cwidget -I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include    -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security  -D_REENTRANT -std=gnu++17 -Wall  -c -o aptitude_resolver.o ../../../../src/generic/apt/aptitude_resolver.cc
> In file included from ../../../../src/generic/apt/apt.cc:55:
> /usr/include/apt-pkg/pkgcachegen.h:32:10: fatal error: xxhash.h: No such file or directory
>    32 | #include <xxhash.h>
>       |          ^~~~~~~~~~
> compilation terminated.
> make[6]: *** [Makefile:582: apt.o] Error 1

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