From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Christian Stewart <christian@paral.in>
Cc: Joel Stanley <joel@jms.id.au>,
"Yann E. MORIN" <yann.morin.1998@free.fr>,
Buildroot Mailing List <buildroot@buildroot.org>
Subject: Re: [Buildroot] [RFC] package/go: switch to gcc go instead of go-bootstrap
Date: Wed, 25 May 2022 23:43:12 +0200 [thread overview]
Message-ID: <20220525234312.643dfc03@windsurf> (raw)
In-Reply-To: <CA+h8R2pE3Z8=fjUBYvXMZp5d3s_+FRQeh4Ms1W8E8eySfdtazA@mail.gmail.com>
Hello Christian,
On Wed, 25 May 2022 14:07:38 -0700
Christian Stewart <christian@paral.in> wrote:
> I propose that we switch to using Gccgo:
>
> - build gcc and/or use external toolchain
> - add flags to enable the "go" language in Gcc
> - GCC 11 or later
The problem I see with this is that many external toolchains do not
provide Go support. While this will probably evolve over time, this is
not something that we can reasonably require right now.
So I believe we probably don't have much other choice but to provide a
path that consists in building Go in multiple stages: first Go 1.4,
then a version of Go that is the last one that can be built with Go
1.4, and use that one to build the latest version of Go.
What do others think?
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-05-25 21:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 21:07 [Buildroot] [RFC] package/go: switch to gcc go instead of go-bootstrap Christian Stewart via buildroot
2022-05-25 21:43 ` Thomas Petazzoni via buildroot [this message]
2022-05-26 2:17 ` Joel Stanley
2022-05-26 13:46 ` Thomas Petazzoni via buildroot
2022-05-27 0:30 ` Christian Stewart via buildroot
2022-05-26 7:43 ` Yann E. MORIN
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=20220525234312.643dfc03@windsurf \
--to=buildroot@buildroot.org \
--cc=christian@paral.in \
--cc=joel@jms.id.au \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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.
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.