Hi Hugh, 1) Does the following patch to libotf fix the issue you are seeing? ---------------------------------------------------------------- # Use pkg-config instead of freetype-config --- a/configure.ac +++ b/configure.ac @@ -49,14 +49,14 @@ AC_FUNC_MALLOC
# Check for Freetype2 usability. -AC_CHECK_PROG(HAVE_FREETYPE_CONFIG, freetype-config, yes) -if test "x$HAVE_FREETYPE_CONFIG" = "xyes"; then - FREETYPE_INC=`freetype-config --cflags` +AC_CHECK_PROG(HAVE_PKG_CONFIG, pkg-config, yes) +if test "x$HAVE_PKG_CONFIG" = "xyes"; then + FREETYPE_INC=`pkg-config freetype2 --cflags` CPPFLAGS="$CPPFLAGS $FREETYPE_INC" AC_CHECK_HEADER(ft2build.h, HAVE_FREETYPE=yes, HAVE_FREETYPE=no CPPFLAGS=$save_CPPFLAGS) if test "x$HAVE_FREETYPE" = "xyes" ; then - FREETYPE_LD_FLAGS=`freetype-config --libs`; + FREETYPE_LD_FLAGS=`pkg-config freetype2 --libs`; LIBS="$LIBS $FREETYPE_LD_FLAGS" AC_CHECK_LIB(freetype, FT_Init_FreeType, HAVE_FREETYPE=yes, HAVE_FREETYPE=no) ---------------------------------------------------------------- 2) I've uploaded binary and source packages to http://hj.id.au/debian/ for you to test. If you are happy with it, I'll upload it to the Debian archives. Thanks, # On 19/10/18 11:45 pm, Hugh McMaster wrote: > Control: severity -1 serious > > Dear maintainer, > > Freetype 2.9.1-2 has been in experimental for three weeks now. As it is > working well, I have decided to upload the package to unstable within the > next two to three weeks. > > A rebuild of your package with freetype 2.9.1 installed confirmed that your > package will FTBFS once the new version of freetype enters unstable. In > almost all cases, this build failure was caused by the configure script not > detecting the freetype libraries, as freetype-config is not shipped in 2.9.1. > > Given the build failure and upcoming upload of freetype 2.9.1, I am raising > the severity of this bug to Serious. > > Please use pkg-config to detect freetype. > > Thank you >