Created attachment 349366 [details] build.log Happens with gcc-4.8.0 and gobject-introspection-1.36.0: $ emerge --info Portage 2.2.0_alpha177 (default/linux/amd64/13.0/developer, gcc-4.8.0, glibc-2.17, 3.9.1 x86_64) ================================================================= System uname: Linux-3.9.1-x86_64-Intel-R-_Core-TM-_i5-2400_CPU_@_3.10GHz-with-gentoo-2.2 KiB Mem: 16395852 total, 4628700 free KiB Swap: 1048572 total, 1048572 free Timestamp of tree: Unknown ld GNU ld (GNU Binutils) 2.23.2 app-shells/bash: 4.2_p45 dev-java/java-config: 2.2.0 dev-lang/python: 2.7.5, 3.2.5, 3.3.2 dev-util/cmake: 2.8.10.2-r2 dev-util/pkgconfig: 0.28 sys-apps/baselayout: 2.2 sys-apps/openrc: 0.11.8 sys-apps/sandbox: 2.6-r1 sys-devel/autoconf: 2.13, 2.69 sys-devel/automake: 1.4_p6-r1, 1.9.6-r3, 1.11.6, 1.13.1 sys-devel/binutils: 2.23.2 sys-devel/gcc: 4.8.0 sys-devel/gcc-config: 1.8 sys-devel/libtool: 2.4.2 sys-devel/make: 3.82-r4 sys-kernel/linux-headers: 3.9 (virtual/os-headers) sys-libs/glibc: 2.17
This bug is supposed to be already fixed in upstream: https://bugs.launchpad.net/lightdm/+bug/1161033
Can confirm upstream patch works, as they fixed it you could do a version bump.
It should be fixed in 1.7.7