From: Efraim Flashner <efraim@flashner.co.il>
To: Leo Famulari <leo@famulari.name>
Cc: 50493@debbugs.gnu.org, Sarah Morgensen <iskarian@mgsn.dev>
Subject: bug#50493: Update go-build-system to use Go 1.17.
Date: Sun, 19 Dec 2021 10:19:02 +0200 [thread overview]
Message-ID: <Yb7q9p8wMUYNOTC9@3900XT> (raw)
In-Reply-To: <Yb0KfWlKHod6aX6U@jasmine.lan>
[-- Attachment #1: Type: text/plain, Size: 1336 bytes --]
On Fri, Dec 17, 2021 at 05:09:01PM -0500, Leo Famulari wrote:
> On Wed, Dec 15, 2021 at 08:03:32PM +0200, Efraim Flashner wrote:
> > I got pretty far commenting out binutils-gold and adding back in gcc:lib
> > and the substitute snippets. Then I started failing tests requiring the
> > linker, so it looks like I'll actually have to troubleshoot
> > binutils-gold.
> >
> > I thought about trying gccgo in place of go-1.4 for the bootstrap, but
> > I'm pretty sure I'd still need binutils-gold.
>
> Maybe, in the meantime, we could update go-build-system to use go-1.16,
> which does at least build on aarch64. This Go release is still
> supported, at least for a little while longer.
>
> It would be nice to not be using Go 1.14 by default in the upcoming
> release.
>
> What do people think about that idea?
All of go is blocked on aarch64 with binutils-gold not compiling. I have
a patch locally to add gcc:lib for (target-arm?) to go-1.17 which I'll
push after testing with binutils-gold. I think going straight to 1.17 is
fine, there's no regression against the current support for aarch64.
--
Efraim Flashner <efraim@flashner.co.il> רנשלפ םירפא
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-12-19 8:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-09 22:14 bug#50493: Update go-build-system to use Go 1.17 Sarah Morgensen
2021-09-09 22:37 ` Leo Famulari
2021-09-20 5:28 ` Sarah Morgensen
2021-12-14 20:11 ` Leo Famulari
2021-12-15 10:40 ` Efraim Flashner
2021-12-15 17:44 ` Leo Famulari
2021-12-15 18:03 ` Efraim Flashner
2021-12-17 22:09 ` Leo Famulari
2021-12-19 8:19 ` Efraim Flashner [this message]
2021-12-20 1:30 ` Leo Famulari
2021-12-20 2:31 ` Leo Famulari
2021-12-24 21:35 ` Leo Famulari
2021-09-20 5:19 ` bug#50493: [PATCH staging 0/4] build-system/go: Use go-1.17 by default Sarah Morgensen
2021-09-20 5:20 ` bug#50493: [PATCH 1/4] build-system/go: Add #:substitutable? argument Sarah Morgensen
2021-09-20 5:20 ` bug#50493: [PATCH 2/4] build-system/go: Initialize build cache from input packages Sarah Morgensen
2021-09-20 5:20 ` bug#50493: [PATCH 3/4] build-system/go: Add pre-built standard library as implicit input Sarah Morgensen
2021-09-20 5:20 ` bug#50493: [PATCH 4/4] build-system/go: Use go-1.17 by default Sarah Morgensen
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=Yb7q9p8wMUYNOTC9@3900XT \
--to=efraim@flashner.co.il \
--cc=50493@debbugs.gnu.org \
--cc=iskarian@mgsn.dev \
--cc=leo@famulari.name \
/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).