On 11 February 2016 at 17:50, Michael Hudson-Doyle <michael.hud...@canonical.com> wrote: > I'm not sure I want to be the one that takes that one upstream.
Totally fair -- I just meant that it's something that probably ought to be taken upstream, not necessarily that I expected you to do so; sorry for the confusion. >> Any chance of tracking down what's causing those to try to go to >> GOROOT instead of GOPATH? > > It's the standard library packages, GOARCH=arm go install runtime is > going to try to create $GOROOT/pkg/linux_arm/runtime.a. This still seems odd to me, especially since doing "GOARCH=arm go build -v my/own/package" clearly does build "runtime" for arm (since it doesn't exist already), but I suppose it doesn't save it anywhere? I would still expect that to go to GOPATH/pkg/linux_arm/... but am not necessarily surprised that it doesn't. :( ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4