9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Philip Silva <philip.silva@protonmail.com>
To: "9front@9front.org" <9front@9front.org>
Subject: Re: [9front] Patch to update Go to 1.14.6 (and ca-certificates while here)
Date: Sat, 09 Jan 2021 19:02:42 +0000	[thread overview]
Message-ID: <Y2XSomn3IALPKgibQUGVKGaXha-_TVjSCG1TyaDccrI2QhN-q4QE7J32iZKSTUuzfRJr99TBMyzLFDgAb8nOrEosz8a0LccYsIA_uH2FQSE=@protonmail.com> (raw)
In-Reply-To: <1F9106FA44696AEEF73230E0CBFD8B15@gmail.com>

For me bootstrapping also worked with the 9legacy Go1.14.1 when doing this on the amd64 iso of 9front - although I had problems in the beginning, maybe because of the env vars. So in the end I've been putting the bootstrapped Go into /usr/glenda/go-plan9-amd64-bootstrap, set the /usr/glenda/env/GOROOT_BOOTSTRAP (bind -a /usr/glenda/env /env) permanently to /usr/glenda/go-plan9-amd64-bootstrap with GOROOT - and I believe also GOPROXY - being unset. Also I've then set: bind -a $home/go-plan9-amd64-bootstrap/bin /bin

Afterwards: cd $home/go1.15.6/src and all.rc. Still need to try the patch though.

By the way, there are also scripts for that, like here: http://shithub.us/git/fulton/rc-scripts/HEAD/install/install-go.rc/f.html

Greetings, Philip

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
Am Mittwoch, 6. Januar 2021 21:45 schrieb <kylejnusbaum@gmail.com>:

> I am using my own amd64 bootstrap tarball for Go built from 1.15.3.
> (http://9project.net/go-plan9-amd64-bootstrap.tar.gz)
>
> Using this, I am able to bootstrap Go on 9front.
>
> As a side note, I used to have trouble using the bootstrap package to
> cross-compile (i.e. using my amd64 bootstrap tarball on amd64 to
> compile plan9 386) so I instead built for plan9 amd64 first, and then
> use that as a bootstrap for any other arches I want, like this:
>
> 1.  go-plan9-amd64-bootstrap.tar.gz to bootstrap Plan9 Go amd64
> 2.  Plan9 Go amd64 to bootstrap other arches (386, arm)
>
>     I just tried it again, and that doesn't seem to be an issue for me
>     anymore, but I thought I'd mention it.
>
>     With the bootstrap unpacked into /sys/lib/go/amd64, my command
>     and output (building 1.15.6 for 386 on amd64) look like this:
>
>     GOOS=plan9 GOARCH=386 GOHOSTARCH=amd64 GOROOT_FINAL=/sys/lib/go/386 GOROOT_BOOTSTRAP=/sys/lib/go/amd64 ./make.rc
>     Building Go cmd/dist using /sys/lib/go/amd64
>     Building Go toolchain1 using /sys/lib/go/amd64.
>     Building Go bootstrap cmd/go (go_bootstrap) using Go toolchain1.
>     Building Go toolchain2 using go_bootstrap and Go toolchain1.
>     Building Go toolchain3 using go_bootstrap and Go toolchain2.
>     Building packages and commands for host, plan9/amd64.
>     Building packages and commands for target, plan9/386.
>
>
> Installed Go for plan9/386 in /9bps/buildroot/go-1.15.6_1/build/go-go1.15.6
> Installed commands in /9bps/buildroot/go-1.15.6_1/build/go-go1.15.6/bin
>
> The binaries expect /9bps/buildroot/go-1.15.6_1/build/go-go1.15.6 to be copied or moved to /sys/lib/go/386



  reply	other threads:[~2021-01-09 19:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-06 14:02 kokamoto
2021-01-06  0:59 ` kylejnusbaum
2021-01-06  5:10   ` kokamoto
2021-01-06  1:37 ` sl
2021-01-06  3:06   ` kokamoto
2021-01-06 20:45     ` kylejnusbaum
2021-01-09 19:02       ` Philip Silva [this message]
2021-01-09 23:24         ` kokamoto
2021-01-10 20:33           ` Philip Silva
2021-01-06  3:06 ` ori
2021-01-06  3:57   ` kokamoto
  -- strict thread matches above, loose matches on Subject: below --
2020-08-06 13:39 Aaron Bieber
2020-08-06 14:02 ` [9front] " kvik
2020-08-06 15:00 ` kvik

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='Y2XSomn3IALPKgibQUGVKGaXha-_TVjSCG1TyaDccrI2QhN-q4QE7J32iZKSTUuzfRJr99TBMyzLFDgAb8nOrEosz8a0LccYsIA_uH2FQSE=@protonmail.com' \
    --to=philip.silva@protonmail.com \
    --cc=9front@9front.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;
as well as URLs for NNTP newsgroup(s).