From: Thiago Jung Bauermann via Bug reports for GNU Guix <bug-guix@gnu.org>
To: iskarian@mgsn.dev
Cc: 49921@debbugs.gnu.org
Subject: bug#49921: go-1.16 build failing on aarch64: "fatal error: runtime.newosproc"
Date: Fri, 10 Sep 2021 20:06:34 -0300 [thread overview]
Message-ID: <12949187.JfoJOkFrob@popigai> (raw)
In-Reply-To: <2cce05f2762e6bb5beadc677a34f00c4@mgsn.dev>
Hello Sarah,
Em sexta-feira, 10 de setembro de 2021, às 19:14:06 -03, iskarian@mgsn.dev
escreveu:
> Hi Thiago,
>
> (Re-sent due to missing Cc.)
>
> September 10, 2021 3:06 PM, "Thiago Jung Bauermann"
<bauermann@kolabnow.com> wrote:
> > Hello Sarah,
> >
> > Em quinta-feira, 2 de setembro de 2021, às 15:47:08 -03, Sarah
> > Morgensen
> >
> > escreveu:
> >> 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.
> >
> > The CI has two native aarch64 builders (which also do armhf, despite
> > bugs 43513 and 43591): dover and overdrive1.
> >
> > It also uses half of the x86_64 builders (hydra-guix-*) for emulated
> > builds of aarch64 and armhf, as can be seen here:
> >
> > https://git.savannah.gnu.org/cgit/guix/maintenance.git/tree/hydra/berli
> > n-nodes.scm#n143
> Thanks for the explanation. Is there a way to tell CI (or Guix itself)
> that certain packages shouldn't be built under emulation?
I don’t know. That would certainly be useful, though.
To be honest, my experience in the past couple of months with emulated
builds for powerpc64le-linux wasn’t good, so I asked for it to be turned
off.
--
Thanks,
Thiago
next prev parent reply other threads:[~2021-09-10 23:07 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
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 [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=12949187.JfoJOkFrob@popigai \
--to=bug-guix@gnu.org \
--cc=49921@debbugs.gnu.org \
--cc=bauermann@kolabnow.com \
--cc=iskarian@mgsn.dev \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).