I would like to try to get an official arm build for 1.6.
I played with the release system a few weeks ago and I think getting an arm binary build out of it should be straight forward.
While we could try all the permutations, I think something at the GOARM=6 level, if it boots on the RPI, should be sufficient.
How does that sound ?
We should send out a Go 1.6 beta 1 soon. What's missing that needs fixing to get into that?Russ
--
You received this message because you are subscribed to the Google Groups "golang-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-dev+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
What about issue https://github.com/golang/go/issues/12278 ("go/build:
honour GO15VENDOREXPERIMENT") ?
While obviouly not critical, perhaps this should be fixed before a go
1.6 beta (since vendoring will be enabled by default) ? A lot of
useful refactoring / code analysis tools are currently (half-)broken
with vendoring and having a fix into go/build ready for 1.6 would
probably allow to easily fix most of them.
I would like to try to get an official arm build for 1.6.
I played with the release system a few weeks ago and I think getting an arm binary build out of it should be straight forward.
While we could try all the permutations, I think something at the GOARM=6 level, if it boots on the RPI, should be sufficient.
How does that sound ?
It should just work.
--