Looking at
https://git.savannah.gnu.org/cgit/guix.git/commit/?id=024a8b39957203f3a3cb93c87746c35635b81e57
it might make sense to do the same for the 'powerpc64le' target as
well?
[Efraim Flashner]:
[...]
just removing the native-inputs field completely from 1.17
should try to
make go-1.17 build with gccgo. Then try to build go@1.17.
That does indeed start a gccgo build and fails after a while with
this:
( https://dpaste.org/3UwS2 has more details)
starting phase
On Thu, Aug 04, 2022 at 11:02:53PM +0200, Marcel van der Boom wrote:
>
> [Efraim Flashner]:
> > I'm currently working on bootstrapping go-1.17.11 directly from gccgo,
> > so we'd be able to skip 1.16 entirely. Currently it works on
> > x86_64-linux but not on riscv64-linux. If you want to test som
[Efraim Flashner]:
I'm currently working on bootstrapping go-1.17.11 directly from
gccgo,
so we'd be able to skip 1.16 entirely. Currently it works on
x86_64-linux but not on riscv64-linux. If you want to test
something
like that on powerpc64le that'd be great.
Sure, can you point me in the
On Thu, Aug 04, 2022 at 06:24:47PM +0200, Marcel van der Boom wrote:
>
> I see that the full build log expired on the paste site.
>
> Is any additional info needed here, other than the excerpt of the log?
>
> I suspect the check error is a safety precaution to ensure executables are
> of reasona
I see that the full build log expired on the paste site.
Is any additional info needed here, other than the excerpt of the
log?
I suspect the check error is a safety precaution to ensure
executables are of reasonable size, but reasonable is perhaps a
bit different on the POWER9 platform?
During the check phase of building go-1.16.15 (as dependency of
ungoogled-chromium) a failure occurs:
https://dpaste.org/ib5CZ :
--- FAIL: TestTrivialExecutable (3.43s)
shared_test.go:484: file too large: got 202752, want <= 10
--- FAIL: TestTrivialExecutablePIE (0.61s)
shared_tes
