On Mon, Mar 13, 2017 at 6:58 PM, Otavio Salvador <[email protected]> wrote: > On Fri, Mar 3, 2017 at 7:19 PM, Khem Raj <[email protected]> wrote: >> * This is converging the recipes for go from >> meta-virtualization and oe-meta-go >> >> * Add recipes for go 1.7 > > Go 1.8 is out so I believe we ought to move to it. Also one thing > which need discussion is regarding the upgrade process of Go recipes. > The 1.8 release is the last one supporting ARMv5 and this means some > reference BSP won't work with Go 1.9 (QEMU ARM) without some hackery. >
As usual in Go community, the things are in a state of flux. The final decision about removing ARMv5 has not been reached yet. While the original proposal was to deprecate ARMv5, members of community have emerged, providing build systems and general argumentation in favor of keeping this target supported (at least for the time being). Right now, the discussion has evolved in the direction of figuring out a general policy for deprecating legacy architectures. Still, there's no guarantee that come 1.9 ARMv5E will be no more. Interested parties can track the progress here: https://github.com/golang/go/issues/17082 and here: https://github.com/golang/go/issues/19075 -- Maciej Borzecki RnDity -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
