From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: Re: [9front] Noob questions
Date: Fri, 19 Jun 2020 16:56:39 -0400 [thread overview]
Message-ID: <6F1CBC14-7BDF-45C4-8060-368E85401BC5@stanleylieber.com> (raw)
In-Reply-To: <B220A456-37CB-4381-A3E5-2F61EB74C161@web.de>
On June 19, 2020 4:40:01 PM EDT, "Alexander Shendi (Web.DE)" <Alexander.Shendi@web.de> wrote:
>
>
>Am 19. Juni 2020 21:01:37 MESZ schrieb "Sigrid Solveig Haflínudóttir" <ftrvxmtrx@gmail.com>:
>>>2. I would like to have a array programming language at my disposal.
>>>Currently the most promising candidate is Rob Pike's Ivy. As it is
>>>written in Go, the way forward is:
>>>2.1 Install a binary package of Go 1.4.3 or 1.14 (done).
>>>2.2 Bootstrap a version of Go that is aber to compile Ivy from it
>>using
>>>the pacjages from step 2.1.
>>>
>>
>>Binary package for Plan 9?
>>I think you can crosscompile on any OS that already has Go:
>>GOOS=plan9 GOARCH=amd64 go build
>
>Thank you for your response.
>Well I obtained a binary package (of sorts) from, I think 9legacy.org. I don't know, if it works properly, though. I have just entered go and saw a help message. I also saw this in the FQA:
>
>NOTE: Go is currently broken on 9front/386. Even 1.4.x versions which used to compile no longer build on 9front/386. 9front/amd64 seems to "work," 1.6.x inclusive. Usual caveats (pending issues) apply.
>
>I guess the way to go is to compile Ivy on OpenBSD as you described and to copy the binary over to 9front.
>
>Many thanks, again,
>
>-- Alexander
>
>
>
>
>--
>You have zero privacy anyway. Get over it.
>
>Scott McNealy 1999
i believe this entry in the fqa is outdated. i haven't tried lately, but i've been told recent go now builds on 386.
sl
next prev parent reply other threads:[~2020-06-19 20:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-19 18:56 Alexander Shendi (Web.DE)
2020-06-19 19:01 ` [9front] " Sigrid Solveig Haflínudóttir
2020-06-19 20:40 ` Alexander Shendi (Web.DE)
2020-06-19 20:56 ` Stanley Lieber [this message]
2020-06-19 20:03 ` Kurt H Maier
2020-06-19 20:08 ` ori
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=6F1CBC14-7BDF-45C4-8060-368E85401BC5@stanleylieber.com \
--to=sl@stanleylieber.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).