On Mon, Nov 13, 2017 at 10:51:10AM -0800, Russ Allbery wrote: > > I'm not sure how best to fix this other than no longer using krb5-config > and shipping a pkgconfig script or something. One could move the > krb5-config script into an architecture-specific directory, but that just > moves the problem to a different area (how to find the right krb5-config > script to use).
Upstream started shipping a pkgconfig script a couple releases ago. I forget whether we do and/or need to patch it to match our configuration. -Ben
