From: Sarah Morgensen <iskarian@mgsn.dev>
To: Leo Famulari <leo@famulari.name>
Cc: 30287-done@debbugs.gnu.org, Peter Mikkelsen <petermikkelsen10@gmail.com>
Subject: bug#30287: Go compiler tries writing to the store
Date: Sat, 24 Jul 2021 17:17:38 -0700 [thread overview]
Message-ID: <86mtqbp7q5.fsf@mgsn.dev> (raw)
In-Reply-To: <86mtr3koud.fsf@mgsn.dev> (Sarah Morgensen's message of "Sat, 03 Jul 2021 15:35:38 -0700")
Closing this as it seems this is no longer an issue with the go versions
currently packaged.
Sarah Morgensen <iskarian@mgsn.dev> writes:
> Hello,
>
> Looking through old Go bugs I found this. Is this still an issue for
> anyone? I just tested with go@1.14 and go@1.16 and I got expected
> behavior (binary was installed in ~/go/bin, since ~/go is the default
> GOPATH).
>
> Leo Famulari <leo@famulari.name> writes:
>
>> On Mon, Jan 29, 2018 at 10:50:10AM +0100, Peter Mikkelsen wrote:
>>> Hi guix,
>>
>> Hi, thanks for this report! I saw your brief conversation on #guix with
>> civodul. Unfortunately I've only been paying attention to packaging Go
>> software with Guix, so I didn't notice this issue.
>>
>>> For example, after setting the environment variable GOPATH to
>>> /home/peter/go, and creating a small hello world program in there, I
>>> would normally be able to run 'go install' in that folder, and the
>>> hello world binary would end up in my gopath. But on guixSD this is
>>> not the case, since it seems like 'go install' is trying to compile
>>> every single library provided by to go package itself, and that means
>>> writing to the store, which is not possible.
>
> --
> Sarah
prev parent reply other threads:[~2021-07-25 0:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-29 9:50 Developing golang programs on guix Peter Mikkelsen
2018-01-29 21:39 ` bug#30287: Go compiler tries writing to the store Leo Famulari
2021-07-03 22:35 ` Sarah Morgensen via Bug reports for GNU Guix
2021-07-25 0:17 ` Sarah Morgensen [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=86mtqbp7q5.fsf@mgsn.dev \
--to=iskarian@mgsn.dev \
--cc=30287-done@debbugs.gnu.org \
--cc=leo@famulari.name \
--cc=petermikkelsen10@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.