usage: build [-o output] [-i] [build flags] [packages] Run 'go help build' for details. * ERROR: dev-go/ed25519-0_pre20160420::gentoo failed (compile phase): * (no error message) * * Call stack: ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-systemd_20180501-115151 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.3.0 * Available Python interpreters, in order of preference: [1] python3.5 [2] python2.7 (fallback) Available Ruby profiles: [1] ruby23 (with Rubygems) * emerge -qpv dev-go/ed25519 [ebuild N ] dev-go/ed25519-0_pre20160420 USE="{-test}"
Created attachment 529366 [details] emerge-info.txt
Created attachment 529368 [details] dev-go:ed25519-0_pre20160420:20180502-101323.log
Created attachment 529370 [details] emerge-history.txt
Created attachment 529372 [details] environment
Created attachment 529374 [details] etc.portage.tbz2
Created attachment 529376 [details] temp.tbz2
This is the culprit I fear: MAKEOPTS="-j1" NINJAFLAGS="-j1" EGO_BUILD_FLAGS="-p1" GOMAXPROCS="1" GO19CONCURRENTCOMPILATION=0 RUSTFLAGS="-C codegen-units=1" RUST_TEST_THREADS=1 RUST_TEST_TASKS=1
*** Bug 654636 has been marked as a duplicate of this bug. ***
Change "-p1" in your EGO_BUILD_FLAGS to "-p 1". According to the output of 'go help build', there must be a space there - not to mention that I have just tested it and it does work that way.