Re: fwupd: FTBFS: ./obj-x86_64-linux-gnu/meson-private/tmp7p7957mh/./obj-x86_64-linux-gnu/meson-private/tmp7p7957mh/testfile.c:17: undefined reference to `gcab_cabinet_add_allowed_compression'
Control: reassign -1 libflashrom-dev 1.3.0-2
Control: affects -1 fwupd
Control: retitle -1 libfrashrom-dev missing dependency on pkg-config required libraries
On Fri, Feb 17, 2023 at 06:34:17AM +0100, Lucas Nussbaum wrote:
> Source: fwupd
> Version: 1.8.10-2
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
> User: lucas@debian.org
> Usertags: ftbfs-20230216 ftbfs-bookworm
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
>
> Relevant part (hopefully):
[...]
I believe this is the actual relevant part:
Called `/usr/bin/pkg-config --cflags flashrom` -> 1
pkg-config error with 'flashrom': Could not generate cargs for flashrom:
Package libjaylink was not found in the pkg-config search path.
Perhaps you should add the directory containing `libjaylink.pc'
to the PKG_CONFIG_PATH environment variable
Package 'libjaylink', required by 'flashrom', not found
> The full build log is available from:
> http://qa-logs.debian.net/2023/02/16/fwupd_1.8.10-2_unstable.log
[...]
grep Requires usr/lib/*-linux-gnu/pkgconfig/flashrom.pc
Requires.private: libpci, libusb-1.0, libftdi1, libjaylink
The packages containing these .pc needs to be listed in
Depends of libflashrom-dev.
I'd suggest adding a trivial compile test as an autopkgtest
using pkgconfig which I find is the easiest way to spot
if the -dev package is missing dependencies listed in the pkg-config
file.
For example see: https://sources.debian.org/src/util-linux/2.38.1-5/debian/tests/libmount-dev/
Regards,
Andreas Henriksson
Reply to: