The recommended way to properly discover this value is pkg-config --variable=pc_path pkg-config, but this gives us the path for pkg-config's architecture. It is where pkgconf stops being Multi-Arch:foreign:
$ bash -c 'exec -a aarch64-linux-gnu-pkgconf pkgconf --variable=pc_path pkg-config'/usr/local/lib/x86_64-linux-gnu/pkgconfig:/usr/local/lib/pkgconfig:/usr/local/share/pkgconfig:/usr/lib/x86_64-linux-gnu/pkgconfig:/usr/lib/pkgconfig:/usr/share/pkgconfig
It looks like upstream has *almost* addressed this problem by refactoring the statically compiled virtual packages into something that could use the cross build personality (but does not yet):
https://github.com/pkgconf/pkgconf/commit/ef935a6349b82259513a1f0cc0cc3180f34a34f5 -- ⢀⣴⠾⠻⢶⣦⠀ ╭────────────────────────────────────────────────────╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │ ⠈⠳⣄⠀⠀⠀⠀ ╰────────────────────────────────────────────────────╯
signature.asc
Description: PGP signature
