From: Sarah Morgensen <iskarian@mgsn.dev>
To: 49921@debbugs.gnu.org
Subject: bug#49921: go-1.16 build failing on aarch64: "fatal error: runtime.newosproc"
Date: Thu, 02 Sep 2021 11:47:08 -0700 [thread overview]
Message-ID: <86v93izufn.fsf@mgsn.dev> (raw)
In-Reply-To: Sarah Morgensen's message of "Fri, 06 Aug 2021 22:04:19 -0700 (3 weeks, 5 days, 13 hours ago)"
Sarah Morgensen <iskarian@mgsn.dev> writes:
> Hello Guix,
>
> I just noticed go-1.16 is failing on aarch64 [0]. I am not having any
> success tracking down the cause. It looks like the error is the same as
> was happening for go-1.14 circa 11 Mar [1], which was fixed by 9 Apr
> [2], but I cannot tell what resolved the issue. I've attached the
> relevant part of the build log; the full log is available at [0].
>
> Any ideas?
>
> [0] https://ci.guix.gnu.org/build/949823/details
> [1] https://ci.guix.gnu.org/build/71004/details
> [2] https://ci.guix.gnu.org/build/19478/details
>
> starting phase `build'
> runtime: failed to create new OS thread (have 2 already; errno=22)
> fatal error: runtime.newosproc
I think this might be related to [0], although if it's true that CI uses
native builders for aarch64 now, I have no idea.
I've been able to reproduce this with both go-1.14 and go-1.16 when
building with --system=aarch64-linux from an amd64 system. I tried to
apply the patch in the thread I mentioned, but go-1.4 won't build at all
with QEMU.
[0] <https://github.com/golang/go/issues/20763> runtime: cannot run
cross compiled ARM binary on QEMU
--
Sarah
next prev parent reply other threads:[~2021-09-02 18:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-07 5:04 bug#49921: go-1.16 build failing on aarch64: "fatal error: runtime.newosproc" Sarah Morgensen
2021-09-02 18:47 ` Sarah Morgensen [this message]
2021-09-10 1:49 ` Sarah Morgensen
2021-09-10 22:06 ` Thiago Jung Bauermann via Bug reports for GNU Guix
2021-09-10 22:14 ` iskarian
2021-09-10 23:06 ` Thiago Jung Bauermann via Bug reports for GNU Guix
2021-12-14 19:29 ` Leo Famulari
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86v93izufn.fsf@mgsn.dev \
--to=iskarian@mgsn.dev \
--cc=49921@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.