Bug 14216 – VTE in GNOME 2.2 RC1 does not compile if HAVE_XFT not set

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Boyd Waters 2003-01-19 22:13:10 UTC]

On some systems (mine), the configure script for VTE may not set HAVE_XFT even
when HAVE_XFT2 is set. This might be due to installing GNOME 2.2 RC1 on a system
with no previous Gnome install.

Resulting compile errors start with something that looks like

vte.c:361: parse error before "XftCharSpec"
vte.c:361: warning: no semicolon at end of struct or union
vte.c:389: parse error before '}' token 

This is GNOME bug 103130 -- it is fixed in CVS.

I have patched the config.in script from the CVS and it now compiles.

I have a revised vte-0.10.8-r1.ebuild that uses this patch.

[Comment 1 Boyd Waters 2003-01-19 22:17:48 UTC]

Created attachment 7459 [details, diff]
Patch to config.in that sets HAVE_XFT if HAVE_XFT2 is set.

I generated this patch against the GNOME VTE from CVS via

diff -u configure.in ~/Projects/GNOME/vte/configure.in

but I removed references to localized strings that are in CVS but not in the
vte-0.10.8 tarball.

[Comment 2 Boyd Waters 2003-01-19 22:21:01 UTC]

Created attachment 7460 [details, diff]
patch that should explain a new VTE ebuild that uses the configure.in patch

I have never written an ebuild.

So I hope that this patch explains the desired effect - we create a new
configure script using the CVS patch before compiling.

This revised ebuild seems to work for me.

[Comment 3 foser (RETIRED) 2003-01-21 13:29:53 UTC]

yeah well, newer version is in portage ;)

thanks anyway

[Comment 4 Boyd Waters 2003-01-23 03:13:15 UTC]

this is the best kind of bug: ignore it and it goes away!

;-)