From: Hank Donnay <hdonnay@gmail.com>
To: 25752@debbugs.gnu.org
Subject: bug#25752: go incremental builds broken
Date: Thu, 16 Feb 2017 10:05:27 -0500 [thread overview]
Message-ID: <CAD4UWkjnkSBYmAfk+E5QAvO9H29Y1xS2vu_h8eB3ZypJ=7NHwg@mail.gmail.com> (raw)
Hello,
It seems the guix's go package is broken when the go tool is used for
incremental builds. Any attempt to use 'install' or 'build -i' results
in an attempt to write to the store. A one-liner:
guix environment --ad-hoc go -- bash -c 'export t=$(mktemp -d); cd
$t && export GOPATH=$(pwd) GOBIN=$(pwd)/bin && go install cmd/go; cd
&& rm -rf $t'
Another command reports that (seemingly) the entire stdlib is marked as stale:
guix environment --ad-hoc go -- bash -c 'export t=$(mktemp -d); cd
$t && export GOPATH=$(pwd) GOBIN=$(pwd)/bin && go list -f '\''{{join
.Deps "\n"}}'\'' cmd/go | xargs -n1 go list -f '\''{{if
.Stale}}{{.ImportPath}}: {{.StaleReason}}{{end}}'\''; cd && rm -rf $t'
The function for determining staleness is here (after the giant
comment explaining the reasoning):
https://golang.org/src/cmd/go/pkg.go#L1111
I don't see anything wrong with the package definition, but could be
missing something. My only hunch at this point is that something might
be modifying src/runtime/internal/sys/zversion.go, as that entire file
is included in the build ID computation.
Thanks,
next reply other threads:[~2017-02-16 15:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-16 15:05 Hank Donnay [this message]
[not found] ` <handler.25752.B.14872575426869.ack@debbugs.gnu.org>
2017-02-24 19:50 ` bug#25752: Acknowledgement (go incremental builds broken) Hank Donnay
2017-02-25 15:58 ` Leo Famulari
2020-12-18 20:00 ` zimoun
2020-12-18 21:31 ` Leo Famulari
2021-01-11 12:46 ` zimoun
2021-01-11 20:01 ` Efraim Flashner
2021-06-09 21:38 ` zimoun
2021-11-26 1:12 ` zimoun
2021-09-14 10:43 ` bug#25752: go incremental builds broken zimoun
2022-10-26 20:42 ` zimoun
2022-10-27 10:21 ` Maxime Devos
2022-10-28 8:22 ` zimoun
2023-10-16 22:44 ` Simon Tournier
2017-03-07 21:50 ` Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAD4UWkjnkSBYmAfk+E5QAvO9H29Y1xS2vu_h8eB3ZypJ=7NHwg@mail.gmail.com' \
--to=hdonnay@gmail.com \
--cc=25752@debbugs.gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).