From: Adrian Bunk <bunk@stusta.de>
To: Daniel Thompson <daniel.thompson@linaro.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] go: Allow bootstrapping using host go compiler
Date: Fri, 12 Apr 2019 22:45:07 +0300 [thread overview]
Message-ID: <20190412194507.GB19080@localhost> (raw)
In-Reply-To: <20190412123046.17510-1-daniel.thompson@linaro.org>
On Fri, Apr 12, 2019 at 01:30:46PM +0100, Daniel Thompson wrote:
> Currently go-native bootstraps without any dependency on the host go
> compiler by building go-1.4 (the last version written in C) and using
> that to build a more recent version of go. This does not work on host
> architectures, such as arm64, that are not supported by go-1.4. To
> support these host architectures we must rely on an existing host go
> compiler and use that to build go-native instead.
>...
Why is this the only option for you?
The clean way to bootstrap go would be by building gccgo and using that
as starting point for the bootstrap.
Haven't tried how trivial or difficult it is to make that work,
but it sounds more long-term maintainable than having different
problems depending on what architecture and host distribution
is used - it doesn't sound like a good idea to have to test
and maintain all combinations, e.g. whether Go 1.6 on arm64
in Ubuntu 16.04 manages to bootstrap the latest Go.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2019-04-12 19:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-12 12:30 [PATCH] go: Allow bootstrapping using host go compiler Daniel Thompson
2019-04-12 12:39 ` Richard Purdie
2019-04-12 13:16 ` Daniel Thompson
2019-04-12 13:34 ` richard.purdie
2019-04-12 14:08 ` Daniel Thompson
2019-04-12 18:26 ` Randy MacLeod
2019-04-12 19:10 ` Adrian Bunk
2019-04-12 19:45 ` Adrian Bunk [this message]
2019-04-24 14:36 ` Daniel Thompson
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=20190412194507.GB19080@localhost \
--to=bunk@stusta.de \
--cc=daniel.thompson@linaro.org \
--cc=openembedded-core@lists.openembedded.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox