From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Re: various problems with installing go lang
Date: Fri, 30 Oct 2020 09:43:20 +0000 [thread overview]
Message-ID: <3e2ec859cd1d005cbafc66652e957048@hamnavoe.com> (raw)
In-Reply-To: <16040252450.A6aD.35871@composer.9fans.topicbox.com>
> I had installed go following
> http://docs.9front.org/building-go
Those instructions don't actually install go into /sys/lib/go/amd64-1.15.2
They install go into /tmp/go, which is then bound dynamically
onto /sys/lib/go/amd64-1.15.2
This has two consequences:
- every time you run go, you must first ensure that /tmp/go is bound onto
$GOROOT in the current process environment
- your /tmp had better not be too temporary (some people use ramfs to mount
/tmp as an in-memory filesystem)
I think it would be safer to install go into the actual /sys/lib tree,
or (eg if you're on a shared system without write permission in /sys/lib),
into your home directory and add the relevant bind command to your
$home/lib/profile
> And other than the go binary I do not see any go files under src.
The .go files are in subdirectories. 'du -a $GOROOT/src' should show
at least 4000 of them.
> Would I even have a cache considering i've never successfully built a go project yet?
Installing go by building from source will cache lots of stuff
in $home/lib/cache/go-build.
next prev parent reply other threads:[~2020-10-30 9:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-24 4:15 nydldmcd2
2020-10-24 4:44 ` [9fans] " Nick Owens
2020-10-24 5:32 ` nydldmcd2
2020-10-24 5:39 ` Nick Owens
2020-10-24 14:38 ` Fazlul Shahriar
2020-10-24 5:29 ` nydldmcd2
2020-10-24 14:15 ` [9fans] " Pavel Renev
2020-10-24 20:59 ` ori
2020-10-27 23:45 ` nydldmcd2
2020-10-28 9:46 ` [9fans] " Richard Miller
2020-10-28 11:00 ` Ethan Gardener
2020-10-28 13:08 ` Richard Miller
2020-10-28 16:13 ` Ethan Gardener
2020-10-30 2:34 ` nydldmcd2
2020-10-30 9:43 ` Richard Miller [this message]
2020-11-01 19:43 ` nydldmcd2
2020-11-02 16:03 ` ori
2021-03-10 17:25 ` ejh
2020-11-01 19:43 ` nydldmcd2
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=3e2ec859cd1d005cbafc66652e957048@hamnavoe.com \
--to=9fans@hamnavoe.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).