go failed to bootstrap with gccgo. My gcc version is 5.3.0 (compiled on March 3, so after go-5 was enabled). Build log: [ebuild U ] dev-lang/go-1.6.1 [1.6-r2] USE="gccgo%*" Would you like to merge these packages? [Yes/No] >>> Verifying ebuild manifests >>> Running pre-merge checks for dev-lang/go-1.6.1 >>> Emerging (1 of 1) dev-lang/go-1.6.1::gentoo * go1.6.1.src.tar.gz SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking go1.6.1.src.tar.gz to /var/tmp/portage/dev-lang/go-1.6.1/work >>> Source unpacked in /var/tmp/portage/dev-lang/go-1.6.1/work >>> Preparing source in /var/tmp/portage/dev-lang/go-1.6.1/work/go ... >>> Source prepared. >>> Configuring source in /var/tmp/portage/dev-lang/go-1.6.1/work/go ... >>> Source configured. >>> Compiling source in /var/tmp/portage/dev-lang/go-1.6.1/work/go ... ##### Building Go bootstrap tool. cmd/dist gcc-config: error: could not run/locate 'go' Reproducible: Always
Sorry for the typo, gcc was compiled on March 30.
Looks like /usr/bin/go-5 can only be run from that folder and does not work when it is symlinked in some other folder
Apparently the gcc-config wrapper can't be symlinked. It was my patch that led to this problem, so I went ahead and fixed it: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=bf6b2654d8d63ffb965881f58d49eb7f832c681c
Thanks! Tested it on amd64 and it worked. However, bootstrap doesn't work on ~arm, it gets stuck in an infinite loop (cmd/dist just never finishes). I guess some bug in gcc...
Exact same bug is back with go-1.6.2
(In reply to jy6x2b32pie9 from comment #5) > Exact same bug is back with go-1.6.2 Fixed now: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=665cebe34f6e452bd138bc6749804e6ffc1cc865
(In reply to Zac Medico from comment #6) > (In reply to jy6x2b32pie9 from comment #5) > > Exact same bug is back with go-1.6.2 > > Fixed now: > > https://gitweb.gentoo.org/repo/gentoo.git/commit/ > ?id=665cebe34f6e452bd138bc6749804e6ffc1cc865 Can you also fix it in -9999 ebuild otherwise it will keep coming back.
(In reply to Andrius Štikonas from comment #7) > Can you also fix it in -9999 ebuild otherwise it will keep coming back. Fixed now: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e9d3e68a0ce0bb76b0fc1f2e58877dbaac63daaa