From: "Aaron Bieber" <aaron@bolddaemon.com>
To: 9front@9front.org
Subject: Re: [9front] Go on ARM64
Date: Fri, 30 Dec 2022 21:04:25 -0700 [thread overview]
Message-ID: <0532b287-0ef8-47a8-b6c4-8a194b070f51@betaapp.fastmail.com> (raw)
In-Reply-To: <8E17625A1D5099AF947E779FA28A9778@thinktankworkspaces.com>
On Fri, Dec 30, 2022, at 7:49 PM, william@thinktankworkspaces.com wrote:
> I couldn't get it to compile. I cloned the repo in /usr/glenda/code and
> changed the path
>
>
> term% GOROOT=/usr/glenda/code/go-arm64.plan9 GOOS=plan9 GOARCH=arm64 make.rc
> go: not found
> go: not found
> ERROR: Cannot find /usr/glenda/go1.4/bin/go.
> Set $GOROOT_BOOTSTRAP to a working Go tree >= Go 1.17.13.
>
> Not sure why its looking for go if i'm compiling for first time
>
> does this matter below?
You need to bootstrap it with an existing go compiler. This is the case on any OS since go is self hosted.
>
> echo go1.20 > VERSION. I have it in both in the following directories.
>
> /usr/glenda/code/go-arm64.plan9/VERSION
> /usr/glenda/code/go-arm64.plan9/src/VERSION
>
>
>
> Quoth Philip Silva <philip.silva@protonmail.com>:
>> Hi!
>>
>> Since I have now a MNT Reform and there was still no Go I tried my luck with porting: https://github.com/psilva261/go-arm64.plan9
>>
>> I've tested compiling from linux/amd64 (Go 1.19.4) and 9front/amd64 (Go 1.18.3), that both works. But since there's no bootstrap.rc, it can be compiled like this:
>>
>> echo go1.20 > VERSION # bootstrap.bash produces something like go1.20-53289fad60
>> cd src
>> GOROOT=/tmp/go-arm64.plan9-arm64.plan9 GOOS=plan9 GOARCH=arm64 make.rc
>> cd .. ; mv bin/plan9_arm64/* bin/
>>
>> Greetings, Philip
>>
>>
prev parent reply other threads:[~2022-12-31 4:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-28 17:29 Philip Silva
2022-12-28 17:51 ` Jacob Moody
2022-12-28 17:58 ` ori
2022-12-28 21:43 ` Philip Silva
2022-12-30 4:59 ` Fazlul Shahriar
2022-12-31 0:44 ` Philip Silva
2022-12-31 1:53 ` Fazlul Shahriar
2022-12-31 2:42 ` ori
2023-01-01 18:06 ` Philip Silva
2022-12-31 2:49 ` william
2022-12-31 4:04 ` Aaron Bieber [this message]
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=0532b287-0ef8-47a8-b6c4-8a194b070f51@betaapp.fastmail.com \
--to=aaron@bolddaemon.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).