a13c62b66b
Upgrade to latest 1.21.x release [1]: $ git --no-pager log --oneline go1.21.5..go1.21.7 f29208030a (tag: go1.21.7) [release-branch.go1.21] go1.21.7 2fdad8af6d [release-branch.go1.21] cmd/internal/obj/arm64: fix frame pointer restore in epilogue 01c93ad049 [release-branch.go1.21] cmd/go/internal/generate: call modload.InitWorkFile db74bfba18 [release-branch.go1.21] Revert "crypto/internal/boring: upgrade module to fips-20220613" +1 916e6cddf1 [release-branch.go1.21] runtime: fix Pinner.Pin documentation 6552f3d4ac [release-branch.go1.21] cmd/go/internal/toolchain: apply the -modcacherw flag when downloading a module to determine what toolchain it needs 3960318b87 [release-branch.go1.21] crypto/x509: properly gate test on macos version 00f974eb1f [release-branch.go1.21] go/types, types2: don't lose position info of interface embeddings 2f91c16e68 [release-branch.go1.21] runtime: properly model rwmutex in lock ranking 2540b1436f [release-branch.go1.21] slices: explicitly discard results of some functions 7e34c4308f [release-branch.go1.21] runtime: clear g0 stack bounds in dropm 491c1e7e95 [release-branch.go1.21] runtime: allow update of system stack bounds on callback from C thread caafb50c0d [release-branch.go1.21] runtime: don't print "unexpected SPWRITE" when printing traceback cc85462b3d (tag: go1.21.6) [release-branch.go1.21] go1.21.6 d2cb140194 [release-branch.go1.21] crypto/tls: align FIPS-only mode with BoringSSL policy 368e2a9461 [release-branch.go1.21] crypto/internal/boring: upgrade module to fips-20220613 8c6078adfb [release-branch.go1.21] runtime: add race annotations in IncNonDefault f6b203c828 [release-branch.go1.21] maps: fix aliasing problems with Clone 43818206dc [release-branch.go1.21] runtime: put ReadMemStats debug assertions behind a double-check mode cf65d74bc5 [release-branch.go1.21] runtime: add the disablethp GODEBUG setting ad1ec60a5b [release-branch.go1.21] runtime/pprof: fix generics function names bbab863ada [release-branch.go1.21] os/signal: skip nohup tests on darwin builders 7dc67e8f29 [release-branch.go1.21] os/signal: remove go t.Run from TestNohup 9f8b3ac8c4 [release-branch.go1.21] cmd/compile: fix escape analysis of string min/max 8c840b10d0 [release-branch.go1.21] cmd/compile: fix memcombine pass for big endian, > 1 byte elements [1] https://github.com/golang/go/compare/go1.21.5...go1.21.7 (From OE-Core rev: 163db4537b5844ff792e9dd462406c2d178939e0) Signed-off-by: Jose Quaresma <jose.quaresma@foundries.io> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Poky
Poky is an integration of various components to form a pre-packaged build system and development environment which is used as a development and validation tool by the Yocto Project. It features support for building customised embedded style device images and custom containers. There are reference demo images ranging from X11/GTK+ to Weston, commandline and more. The system supports cross-architecture application development using QEMU emulation and a standalone toolchain and SDK suitable for IDE integration.
Additional information on the specifics of hardware that Poky supports is available in README.hardware. Further hardware support can easily be added in the form of BSP layers which extend the systems capabilities in a modular way. Many layers are available and can be found through the layer index.
As an integration layer Poky consists of several upstream projects such as BitBake, OpenEmbedded-Core, Yocto documentation, the 'meta-yocto' layer which has configuration and hardware support components. These components are all part of the Yocto Project and OpenEmbedded ecosystems.
The Yocto Project has extensive documentation about the system including a reference manual which can be found at https://docs.yoctoproject.org/
OpenEmbedded is the build architecture used by Poky and the Yocto project. For information about OpenEmbedded, see the OpenEmbedded website.
Contribution Guidelines
Please refer to our contributor guide here: https://docs.yoctoproject.org/dev/contributor-guide/ for full details on how to submit changes.
Where to Send Patches
As Poky is an integration repository (built using a tool called combo-layer), patches against the various components should be sent to their respective upstreams:
OpenEmbedded-Core (files in meta/, meta-selftest/, meta-skeleton/, scripts/):
- Git repository: https://git.openembedded.org/openembedded-core/
- Mailing list: openembedded-core@lists.openembedded.org
BitBake (files in bitbake/):
- Git repository: https://git.openembedded.org/bitbake/
- Mailing list: bitbake-devel@lists.openembedded.org
Documentation (files in documentation/):
- Git repository: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-docs/
- Mailing list: docs@lists.yoctoproject.org
meta-yocto (files in meta-poky/, meta-yocto-bsp/):
- Git repository: https://git.yoctoproject.org/cgit/cgit.cgi/meta-yocto
- Mailing list: poky@lists.yoctoproject.org
If in doubt, check the openembedded-core git repository for the content you intend to modify as most files are from there unless clearly one of the above categories. Before sending, be sure the patches apply cleanly to the current git repository branch in question.