The subject says all. The error is vte.c: In function ‘vte_terminal_paint_area’: vte.c:10357: error: implicit declaration of function ‘GTK_WIDGET_DOUBLE_BUFFERED’ vte.c:10357: warning: nested extern declaration of ‘GTK_WIDGET_DOUBLE_BUFFERED’ I bumped the ebuild to 0.23.5 and, despite a good number of warnings, it builds successfully. Reproducible: Always
Created attachment 221105 [details] vte-0.22.5 build log
Created attachment 221109 [details] vte-0.23.5 build log with all the warnings Looking at the configure script the only difference in dependencies is about glib, previously >=2.18.0 and now >=2.22.0.
Pushed x11-libs/vte-0.23.5 to tree, so this should fix it.
The bug happens also with vte-0.22.5 against gtk+-2.19.6, vte-0.23.5 builds fine.
Since vte-0.23.5 has been added to overlay, marking this as FIXED.
What was the exact problem that the newer VTE now fixed? I'm worried about API compatibility of gtk+ here
(In reply to comment #6) > What was the exact problem that the newer VTE now fixed? I'm worried about API > compatibility of gtk+ here > The problem was that after bumping gtk+ in the tree, vte-0.22.5 didn't build anymore because it was using deprecated functionality. ABI didn't seem to be changed.
So it fails to compile only because VTE development versions are being compiled with G_DISABLE_DEPRECATED (as intended)? But then vte-0.22 wouldn't have failed. So basically you are confirming that this is an API break in gtk+? GTK+ has to provide not only ABI backwards compatibility across 2.x series, but also API
It fails also with gtk+-2.20.0.
In which overlay can vte-0.23.5 be found?
Gnome overlay. You can find vte-0.24 there, too.
I think this is not fixed, if ~arch x11-libs/vte does not compile against ~arch x11-libs/gtk+ from main portage tree.
>=gtk-2.19 is not ~arch, it's overlay.