From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/go: bump version to 1.6.2
Date: Sun, 8 May 2016 14:39:56 +0200 [thread overview]
Message-ID: <20160508143956.4b5a4db0@free-electrons.com> (raw)
In-Reply-To: <CABa6e=og-BDA_VY=wJ17uc9=-S0D34SEstRv1W_FyFVUU=ehcw@mail.gmail.com>
Hello,
On Sun, 8 May 2016 06:55:36 +1000, Cam Hutchison wrote:
> > As far as I understand, we can't use go 1.5.2 as the bootstrap
> > compiler, because since 1.5.x, Go is written in Go. I guess we will
> > have to backport the patch.
>
> I think it should be sufficient to build the go-bootstrap compiler with
> "CGO_ENABLED=0" in its environment. This worked for me when I
> played with it and looks like the correct solution according to
> https://github.com/golang/go/issues/13114
When the packaging of Go was added to Buildroot, I was pointed to
https://docs.google.com/document/d/1OaatvGhEAq7VseQ9kkavxKNAfepWy2yhPUBs96FGV28/edit,
which says that using Go 1.4 as the bootstrap compiler to build Go 1.5
was the proper solution.
Now, if it is possible to use a two-stage build of go 1.5, then that's
also fine with me, but it somewhat contradicts the above document.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-05-08 12:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-06 16:23 [Buildroot] [PATCH 1/1] package/go: bump version to 1.6.2 Christian Stewart
2016-05-06 18:01 ` Geoff Levand
2016-05-07 12:43 ` Thomas Petazzoni
2016-05-07 13:05 ` Christian Stewart
2016-05-07 12:43 ` Thomas Petazzoni
2016-05-07 18:45 ` Baruch Siach
2016-05-07 19:40 ` Thomas Petazzoni
2016-05-07 20:55 ` Cam Hutchison
2016-05-08 12:39 ` Thomas Petazzoni [this message]
2016-05-08 12:46 ` Cam Hutchison
2016-05-08 12:59 ` Thomas Petazzoni
2016-05-10 17:37 ` Geoff Levand
2016-05-10 18:02 ` [Buildroot] [PATCH v2 " Geoff Levand
2016-05-10 18:12 ` Geoff Levand
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=20160508143956.4b5a4db0@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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