x11-libs/libxkbcommon-9999 fails to build. At first i thought it was a temporary problem with git, but according to git log the repository hasn't been touched for weeks. Reproducible: Always
Created attachment 311119 [details] build log
% emerge --info Portage 2.1.10.56 (default/linux/amd64/10.0/desktop, gcc-4.6.2, glibc-2.14.1-r2, 3.3.4-hgv3.3.4-dirty x86_64) ================================================================= System uname: Linux-3.3.4-hgv3.3.4-dirty-x86_64-AMD_Athlon-tm-_II_X4_620_Processor-with-gentoo-2.1 Timestamp of tree: Fri, 04 May 2012 16:45:01 +0000 app-shells/bash: 4.2_p24 dev-java/java-config: 2.1.11-r3 dev-lang/python: 2.7.2-r3 dev-util/cmake: 2.8.7-r2 dev-util/pkgconfig: 0.26 sys-apps/baselayout: 2.1 sys-apps/openrc: 0.9.9.3 sys-apps/sandbox: 2.5 sys-devel/autoconf: 2.13::<unknown repository>, 2.68 sys-devel/automake: 1.9.6-r3, 1.11.3 sys-devel/binutils: 2.22-r1 sys-devel/gcc: 4.6.2, 4.7.0::freehackers sys-devel/gcc-config: 1.7 sys-devel/libtool: 2.4.2 sys-devel/make: 3.82-r3 sys-kernel/linux-headers: 3.2 (virtual/os-headers) sys-libs/glibc: 2.14.1-r2
After investigating, upstream knew about this issue, and have fixed it. But the gentoo ebuild still wont work because it uses srcdir!=builddir and this is broken upstream. Is there a way to NOT do this ? The live ebuild is empty and rely on some eclass.. that's where my ability to understand ebuild stops :-(
i confirm it works if doing export AUTOTOOLS_IN_SOURCE_BUILD=1 before emerge... Upstream is aware of the bug and this should be fixed soon. So closing this one.
