Red Hat Bugzilla – Bug 173541
xterm builds without freetype support if xft-config is not found, even though freetype-config is available
Last modified: 2007-11-30 17:11:17 EST
Description of problem:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Run "xterm -fa Monospace -fs 10"
You get an unrecognized argument error.
Xterm starts up.
The configure test for freetype-config fails because the previous test for
checking if you want to use FreeType library... yes
checking for xft-config... none
checking for freetype-config... (cached) no
Created attachment 121212 [details]
patch to discard the cached result before checking if freetype-config is available
xft-config has been deprecated for about 2 years or so, and Xft has shipped
pkg-config *.pc files. xft-config now no longer exists in modular X, and
applications using libXft must now transition to using pkg-config in order
to build properly.
Example usage for fixing xterm:
pts/1 mharris@fc4i386:~/rpmbuild/SRPMS$ pkg-config xft --libs
-lXft -lfreetype -lz -lXrender -lX11 -ldl -lfontconfig
pts/1 mharris@fc4i386:~/rpmbuild/SRPMS$ pkg-config xft --cflags
Yes, this was fixed with xterm-207-2 (though not as portably as with your
suggestion). I've now patched xterm's configure to use pkg-config instead of
looking for xft-config / freetype-config with xterm-207-4 . It would have been
nice to be able to patch configure.in, but configure is generated by a
customized autoconf used only by the upstream maintainer. I've sent the
patch upstream, so hopefully it will be in the next release. Thanks!