Hi Helmut, 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?
That aside, calling `freetype-config` or `pkg-config --libs freetype2` when libfreetype6-dev is installed only for a foreign architecture does emit those errors, which is a problem. We can fix that by modifying freetype-config. See the attached patch for a draft fix. The patch handles some pkg-config use cases and has a fallback to the autoconf values in the case where libfreetype6-dev is installed only for a foreign architecture and PKG_CONFIG_LIBDIR is not set. The fallback is useful, since `freetype-config --libs` outputs -lfreetype, so the linker can work out the libdir path. > 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. Remember, freetype-config was never designed for cross-compiling. So it's debatable whether we should (attempt to) support this. Another question to think about is whether Debian's freetype-config should wrap pkg-config at all. -- Hugh McMaster
freetype-config.diff
Description: freetype-config.diff
