9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Lucio De Re <lucio.dere@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] go1.13.1 build fails
Date: Mon, 7 Oct 2019 10:36:53 +0200	[thread overview]
Message-ID: <CAJQ9t7gfXcopCsDyzYL05QYTT-jL6NdJB00p9oVEhMXtU2uriw@mail.gmail.com> (raw)
In-Reply-To: <7aecf568-abda-4ce3-a97b-1f481491da45@www.fastmail.com>

In fact, I'd forgotten I'd had an exchange with a Go developer (I wish
I could remember who) precisely over that "bootstrap" issue. Go1.4.3
needs a small enhancement, I forget from which target onwards because
of some executable binary improvement even for Linux. But the
bootstrap version is the recommended one, recently, as I mentioned.

Here is Brad's message:

--- cut ---
You'll want to use the release-branch.go1.4 branch, not Go 1.4.3.

See https://golang.org/doc/install/source#go14 which says:

> To build a bootstrap toolchain from source, use either the git branch release-branch.go1.4 or go1.4-bootstrap-20171003.tar.gz, which contains the Go 1.4 source code plus accumulated fixes to keep the tools running on newer operating systems. (Go 1.4 was the last distribution in which the toolchain was written in C.) After unpacking the Go 1.4 source, cd to the src subdirectory, set CGO_ENABLED=0 in the environment, and run make.bash (or, on Windows, make.bat).

--- cut ---

On 10/7/19, David du Colombier <0intro@gmail.com> wrote:
> I'd recommend bootstrapping Go with one of
> the recent binary package available on:
>
> http://9legacy.org/download.html
>
> There might be issues when bootstrapping from Go 1.4.
> Also, plan9/arm support started with Go 1.7.
>
> --
> David du Colombier
>
>


-- 
Lucio De Re
2 Piet Retief St
Kestell (Eastern Free State)
9860 South Africa

Ph.: +27 71 471 3694
Cell: +27 83 251 5824



  reply	other threads:[~2019-10-07  8:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-04 21:53 Skip Tavakkolian
2019-10-05  1:41 ` Sean Hinchee
2019-10-06 11:09 ` Richard Miller
2019-10-07  3:54   ` Skip Tavakkolian
2019-10-07  7:46     ` David du Colombier
2019-10-07  8:36       ` Lucio De Re [this message]
2019-10-11 16:26         ` Jerome Ibanes
2019-10-16 16:01           ` Juan Cuzmar
2019-10-17  1:58             ` Sean Hinchee
2019-10-17  2:07               ` Juan Cuzmar

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=CAJQ9t7gfXcopCsDyzYL05QYTT-jL6NdJB00p9oVEhMXtU2uriw@mail.gmail.com \
    --to=lucio.dere@gmail.com \
    --cc=9fans@9fans.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;
as well as URLs for NNTP newsgroup(s).