From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Re: various problems with installing go lang
Date: Wed, 28 Oct 2020 09:46:55 +0000 [thread overview]
Message-ID: <615e7ff79ac2b0a83a73c4191eaa75b1@hamnavoe.com> (raw)
In-Reply-To: <16038423400.fe5e1.29105@composer.9fans.topicbox.com>
> hget http://sprunge.us/3hcWI4
The first error message is:
../go/pkg/mod/github.com/henesy/disco@v0.0.0-20200313024015-ff90b1ac381a/config.go:4:2: package bufio is not in GOROOT (/sys/lib/go/amd64-1.15.2/src/bufio)
That's telling you that it's attempting to rebuild some of the go library.
(Don't ask why. Rather than use something understandably deterministic like mk,
the go authors have opted for an inference engine to detect "staleness",
which, in my experience, can trigger a recompile of the entire library
when something apparently innocent is touched.)
Does the source directory it's mentioning exist, and have .go files in it?
Do you have write permission in the $GOROOT/pkg tree?
Giving your go build cache a good clean might help. Or it might break
everything completely, so make a backup first.
next prev parent reply other threads:[~2020-10-28 9:47 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 ` Richard Miller [this message]
2020-10-28 11:00 ` [9fans] " 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
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=615e7ff79ac2b0a83a73c4191eaa75b1@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).