Created attachment 291981 [details, diff] vala-0.12.1-multilib-tests.patch The tests always fail for ABI=x86 when running under portage-multilib on an amd64 machine. The reason is that -m32 is not being passed to the computer by the VALAC. The particular build error in the build.log is caused by a mismatch between glib headers and gcc's compilation mode: ohnobinki@ohnopublishing ~ $ ABI=amd64 pkg-config --cflags glib-2.0 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include ohnobinki@ohnopublishing ~ $ ABI=x86 pkg-config --cflags glib-2.0 -I/usr/include/glib-2.0 -I/usr/lib32/glib-2.0/include ohnobinki@ohnopublishing ~ $ grep -R -e typedef.\*gsize /usr/lib*/glib-2.0/include /usr/lib32/glib-2.0/include/glibconfig.h:typedef unsigned int gsize; /usr/lib64/glib-2.0/include/glibconfig.h:typedef unsigned long gsize; The negative array reference is when sizeof(gsize) != sizeof(gpointer) in the definition of g_atomic_pointer_get() by the glib/gatomic.h header. It is apparently a sanity check of some sort. Of course, when -m32 is used sizeof(int) == sizeof(void*). But when -m32 is forgotten, the error condition of sizeof(int) != sizeof(void*) is encountered. The attached patch incorporates CFLAGS from the environment and fixes this problem.
Created attachment 291983 [details] vala-0.12.1-build.log
Created attachment 291985 [details] emerge--info.txt
I would send this to upstream also: bugzilla.gnome.org
(In reply to comment #3) > I would send this to upstream also: bugzilla.gnome.org Did you reported this?
(In reply to comment #4) > (In reply to comment #3) > > I would send this to upstream also: bugzilla.gnome.org > > Did you reported this? No. I might if I have time, unfortunately I might forget to do so altogether :-/.
Upstream bug filed at https://bugzilla.gnome.org/show_bug.cgi?id=664606, thanks for the poking ;-).
(In reply to comment #6) > Upstream bug filed at https://bugzilla.gnome.org/show_bug.cgi?id=664606, thanks > for the poking ;-). Looks like upstream think honor CPPFLAGS wouldn't be needed, could you reply to him there please? Thanks
Thanks again for the poke. Upstream has committed the fix to their git repo, in case if that is justification enough to start applying the upstreamed patch to gentoo-x86 ;-).
From my point of view, feel free to apply it to latest vala version if you need the fix already, if not, we will probably wait for next version ;)
vala-0.16 was added