On Friday, 17 November 2017 7:26 AM, Sam Hartman wrote: > Also, if we're moving away from krb5-config, the only strong requirement > is that krb5-config work correctly on the native architecture. > We'd like it to work in other cases, but if we're OK telling people who > are cross-compiling to use pkgconfig then it's OK if krb5-config is > imperfect. > While I think we can do better, even just having unqualified > krb5-config.mit be for the native architecture would not make things > worse than today.
I spent some time looking into this today, and I think it's worth pointing out that pkg-config can produce the correct library path if invoked using pkg-config-crosswrapper, e.g. i686-linux-gnu-pkg-config. This raises the possibility that krb5-config could become a wrapper script for pkg-config, rather than a wrapper for arch-specific krb5-config scripts. With this in mind, I wrote a proof-of-concept script for testing. It's not perfect by any means, but it's one way of moving forward. The script relies on CC being set in the shell environment. -- Hugh McMaster
krb5-pkg-config
Description: krb5-pkg-config
