checking whether to add custom build version... no
checking whether to build with Java support... no
configure: WARNING: building without java will mean some features will not be available
checking whether to enable EPM for packing... yes
checking for epm... /usr/local/bin/epm
checking whether the found EPM is the right EPM... yes
checking EPM version... OK, >= 5.0
checking which package format to use... rpm
checking for rpm... /usr/bin/rpmbuild
checking for gperf... /usr/bin/gperf
checking for gperf... (cached) /usr/bin/gperf
checking gperf version... OK
checking whether to build the stax... yes
checking whether to build the ODK... yes
checking whether to provide libstdc++/libgcc_s in the installset... yes
checking which zlib to use... internal
checking which jpeg to use... internal
checking which expat to use... internal
./configure: line 13977: syntax error near unexpected token `FREETYPE,'
./configure: line 13977: ` PKG_CHECK_MODULES( FREETYPE, freetype2 >= 2.0 )'
[Helena@hV61n main]$ pkg-config --modversion freetype2
26.2.20
[Helena@hV61n main]$ ls /usr/lib/pkgconfig/ | grep freetype
freetype2.pc
[Helena@hV61n main]$ ls /usr/share/aclocal/ | grep pkg
coin_chk_pkg.m4
pkg.m4
[Helena@hV61n main]$
Todo indica que pkg-config detecta correctamente freetype2, ya que:
pkg-config --modversion freetype2 devuelve 26.2.20, lo que significa que la versión de freetype2 está disponible.
ls /usr/lib/pkgconfig/ | grep freetype muestra freetype2.pc, lo que confirma que el archivo de configuración está en la ubicación correcta.
El error syntax error near unexpected token 'FREETYPE,' sugiere que autoconf o autoreconf no está procesando correctamente la macro PKG_CHECK_MODULES.