Below commits on glibc-2.35 stable branch are updated. 37214df5f1 libio: Attempt wide backup free only for non-legacy code 09fb06d3d6 nptl: Use <support/check.h> facilities in tst-setuid3 507983797e posix: Use <support/check.h> facilities in tst-truncate and tst-truncate64 bcd0e854ea ungetc: Fix backup buffer leak on program exit [BZ #27821] e930b89df7 ungetc: Fix uninitialized read when putting into unused streams [BZ #27821] a3db6ce751 Make tst-ungetc use libsupport ed9762fdbf stdio-common: Add test for vfscanf with matches longer than INT_MAX [BZ #27650] cf71d2189c support: Add FAIL test failure helper 5b4e90230b stdio-common: Reformat Makefile. 3c64e961ff Fix name space violation in fortify wrappers (bug 32052) ba003ee5de resolv: Fix tst-resolv-short-response for older GCC (bug 32042) 5a1d0633be Add mremap tests 0ff91d3961 mremap: Update manual entry 7459b6fe47 linux: Update the mremap C implementation [BZ #31968] 461d0cac38 tests: replace system by xsystem 041ac9dffe resolv: Track single-request fallback via _res._flags (bug 31476) 820a750bed resolv: Do not wait for non-existing second DNS response after error (bug 30081) 4f5aa1d2fb resolv: Allow short error responses to match any query (bug 31890) a180e82837 Linux: Make __rseq_size useful for feature detection (bug 31965) f8a52d39c0 elf: Make dl-rseq-symbols Linux only d36daa4c01 nptl: fix potential merge of __rseq_* relro symbols 602fff4efa Add AT_RSEQ_* from Linux 6.3 to elf.h c7cd626538 s390x: Fix segfault in wcsncmp [BZ #31934] (From OE-Core rev: db4cee587fe43f93a9bc9a1356c65a50f92085d9) Signed-off-by: Deepthi Hemraj <Deepthi.Hemraj@windriver.com> Signed-off-by: Steve Sakoman <steve@sakoman.com>
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
The project works using a mailing list patch submission process. Patches should be sent to the mailing list for the repository the components originate from (see below). Throughout the Yocto Project, the README files in the component in question should detail where to send patches, who the maintainers are and where bugs should be reported.
A guide to submitting patches to OpenEmbedded is available at:
https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded
There is good documentation on how to write/format patches at:
https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
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.