On 2025-01-22 20:28:38, Andrej Shadura wrote:
It's not *just* a symlink. Pkgconf behaves differently depending on what name it's called as. Have you actually tried it?
Yes, yes I had - and just did it again: $ x86_64-linux-gnu-pkgconf --variable pc_path pkgconf /usr/local/lib/i386-linux-gnu/pkgconfig:/usr/local/lib/pkgconfig:/usr/local/share/pkgconfig:/usr/lib/i386-linux-gnu/pkgconfig:/usr/lib/pkgconfig:/usr/share/pkgconfig What I apparently did not see before though, was that $ x86_64-linux-gnu-pkgconf --cflags jsoncpp -I/usr/include/jsoncpp I suspect that was because by the time I learned about x86_64-linux-gnu-pkgconf, I was already to the point in my troubleshooting of directly checking the --variable pc_path option. So I'd still consider it a bug in that 1) my original point stands: there's no reason for pkgconf (even without a symlink call) to assume any specific architecture for libraries on multiarch systems, especially not based on the binary architecture of pkgconf itself 2) the config output of --variable pc_path should also respect that "what name it's called as" And I stand by my "it would be appreciated if this can be fixed" :) Kind regards Lars
