Package: pkgconf Version: 1.6.3-4 Severity: normal Tags: patch The pkg-config-crosswrapper script uses dpkg-architecture (part of dpkg-dev) internally; if that package is not installed, the script will not fail explicitly, but happily report incorrect information instead.
For example, on an x86_64 machine that is set up to cross-compile for aarch64 $ dpkg -l libglib2.0-dev:arm64 | tail -1 ii libglib2.0-dev:arm64 2.58.3-2+deb10u2 arm64 Development files for the GLib library $ when dpkg-dev is installed pkgconf behaves as expected $ aarch64-linux-gnu-pkg-config --path glib-2.0 /usr/lib/aarch64-linux-gnu/pkgconfig/glib-2.0.pc $ whereas uninstalling dpkg-dev results in $ aarch64-linux-gnu-pkg-config --path glib-2.0 $ I'll open a MR on Salsa in a minute. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (900, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages pkgconf depends on: ii libc6 2.29-10 ii libdpkg-perl 1.19.7 ii perl 5.30.0-9 pkgconf recommends no packages. pkgconf suggests no packages. -- no debconf information
