Sam Hartman <hartm...@debian.org> writes: > we do ship a pkg-config script and that handles this correctly. > How does pkg-config figure out which arch you're building for?
pkg-config the command appears to have the same problem. It embeds a compile-time path of pkgconfig directories to search for build options, which is based on the architecture for which pkg-config is built: lothlorien:~$ strings /usr/bin/pkg-config | grep /pkgconfig /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 So the Debian package containing pkg-config the binary can't really be multiarch, and it will return whatever flags are appropriate for building a native binary on the architecture for which it was built. pkgconfig the Autoconf system can use config.guess and related Autoconf machinery to know the target architecture and then use the correct pkgconfig files for that architecture, although I haven't played with it enough to know exactly how (or if) that's wired together. -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
