On Sun, Jan 07, 2018 at 12:14:20PM +0000, Hugh McMaster wrote: > On Saturday, 6 Jan 2018 11:59:23 +0100, Helmut Grohne wrote: > Did you set PKG_CONFIG_LIBDIR to /usr/lib/i386-linux-gnu/pkgconfig?
No. One is not supposed to set PKG_CONFIG_LIBDIR as it breaks the cross wrapper and thus breaks using the build arch and host arch pkg-config. > > Since the behaviour of this tool (being part of the API of the package) > > is significantly different, I conclude that libfreetype6-dev is wrongly > > marked M-A:same. Please remove the marking. > It's taken a lot of time to get M-A: same, so I'd prefer this not to happen. I'm with you here. I just value correct M-A:same > no M-A > broken M-A:same. > Remember, freetype-config was never designed for cross-compiling. > So it's debatable whether we should (attempt to) support this. I agree. How about removing it from the package? It's not that many reverse dependencies to fix. > Another question to think about is whether Debian's freetype-config > should wrap pkg-config at all. Probably not, because pkg-config is only reliable when you add an architecture prefix. Something that freetype-config cannot do. So if you don't dump it, it probably shouldn't try using pkg-config at all. At the very least removing one of the two implementations (with/without pkg-config) would help a lot with ensuring that it actually works. The current way is annoying as the failure mode depends on pkg-config being installed. I don't think having libfreetype6-dev depends: pkg-config would be too bad either. Helmut
