Created attachment 403352 [details] bug fix patch When emerging with FEATURES=splitdebug dev-lang/go and dev-lang/go-bootstrap have the same debug build-id for the file src/debug/dwarf/testdata/typedef.elf. * Detected file collision(s): * * /usr/lib/debug/.build-id/3c/bafbed5802dff5c21b34efcb0c6eb249a408ac.debug * /usr/lib/debug/.build-id/3c/bafbed5802dff5c21b34efcb0c6eb249a408ac
bump
You probably need to rebuild gcc; the build-id stuff has been disabled for months. See bug 526144.
Reopening, it's slightly more interesting than that. I'm getting this with a fairly recently built gcc-4.9.3 (from July 2nd this year, so half a year more recent than that bug). The collision is on: * dev-lang/go-1.4.2:0::gentoo * /usr/lib/debug/.build-id/3c/bafbed5802dff5c21b34efcb0c6eb249a408ac * /usr/lib/debug/.build-id/3c/bafbed5802dff5c21b34efcb0c6eb249a408ac.debug The former is a symlink to /usr/lib/go/src/debug/dwarf/testdata/typedef.elf. This is in fact a testdata file that's included in the go1.4.2.src.tar.gz tarball: % tar xf /usr/portage/distfiles/go1.4.2.src.tar.gz % file ./go/src/debug/dwarf/testdata/typedef.elf ./go/src/debug/dwarf/testdata/typedef.elf: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.15, BuildID[sha1]=3cbafbed5802dff5c21b34efcb0c6eb249a408ac, not stripped I suspect the toolchain used to create this file had "the build-id stuff" enabled, and that's biting us. The source for the testdata file seems to be included (go/src/debug/dwarf/testdata/typedef.c). One workaround might be to rebuild the testdata file in the ebuild. Another workaround might be to remove the problematic testdata from go-bootstrap, only keeping it in go proper. In the mean time, I'll go see if downgrading go works around this.
...that was a silly suggestion, there is no older go ebuild in the tree.
Created attachment 409784 [details, diff] dev-lang/go-bootstrap: avoid stripping test data files Another way to resolve this issue is to simply avoid stripping test data files as the latest go-9999 ebuild does. Here's a ebuild patch to do just that :)
*** Bug 558400 has been marked as a duplicate of this bug. ***
The patch in comment #5 was applied, thanks much. Let me know if this is still an issue. William