When invoked as $triplet-pkg-config, pkg-config is smart enough to search the paths corresponding to the target architecture; on Debian, however, this currently only works when dpkg-dev is installed, which by default it is not. Work around the issue on our side by installing dpkg-dev explicitly in our cross-building container images. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952526 Signed-off-by: Andrea Bolognani <abologna@xxxxxxxxxx> --- guests/lcitool | 1 + 1 file changed, 1 insertion(+) diff --git a/guests/lcitool b/guests/lcitool index 771402e..86416c4 100755 --- a/guests/lcitool +++ b/guests/lcitool @@ -811,6 +811,7 @@ class Application: dpkg --add-architecture {cross_arch} && \\ {package_manager} update && \\ {package_manager} dist-upgrade -y && \\ + {package_manager} install --no-install-recommends -y dpkg-dev && \\ {package_manager} install --no-install-recommends -y {cross_pkgs} && \\ {package_manager} autoremove -y && \\ {package_manager} autoclean -y -- 2.24.1
