Created attachment 369914 [details]
x11-libs/mx-1.4.7-r1 fails to build because of a stray "=1":
/bin/sh ../libtool --tag=CC --mode=compile x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -DG_LOG_DOMAIN=\"MxGtk\" -Wall -DG_DISABLE_ASSERT -DG_DISABLE_CHECKS -DG_DISABLE_CAST_CHECKS -pthread -I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libdrm -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/libpng16 =1 -ggdb -O2 -pipe -march=native -c -o libmx_gtk_1.0_la-mx-gtk-frame.lo `test -f '../mx-gtk/mx-gtk-frame.c' || echo './'`../mx-gtk/mx-gtk-frame.c
x86_64-pc-linux-gnu-gcc: error: =1: No such file or directory
mx-1.4.7 is fine. Comparing their config.log, we see GTK_CFLAGS includes -DGSEAL_ENABLE=1 in 1.4.7, which is turned into =1 in 1.4.7-r1. That's probably done by the sed in gnome2_disable_deprecation_warning, which is called via gnome2_src_prepare which got added to the ebuild in 1.4.7-r1.
I suspect the correct fix is to make that sed remove any trailing =1 as well, but I'm not hindered by knowledge of how GSEAL_ENABLE is "normally" used :)
Created attachment 369916 [details]
same here, have to skip it to continue then.
Sorry, this is because I needed to modify it while running repoman due a warning :S, let me check in some minutes
+ 09 Feb 2014; Pacho Ramos <firstname.lastname@example.org> gnome2-utils.eclass:
+ Drop also values of DGSEAL_ENABLE (#500730)
Try this, looks to work ok for me (I still don't understand why it merged ok for me yesterday while not doing once I added the subslot stuff for cogl :S)
*** Bug 500754 has been marked as a duplicate of this bug. ***
Much better, thanks!