b0d4d9fbbf
Below commits on glibc-2.37 stable branch are updated. 3593050c27 (HEAD -> release/2.37/master, origin/release/2.37/master) io: Fix F_GETLK, F_SETLK, and F_SETLKW for powerpc64 e2974d26ce io: Fix record locking contants on 32 bit arch with 64 bit default time_t 0e3e9dbb0e Document BZ #20975 fix f5d377c896 __check_pf: Add a cancellation cleanup handler [BZ #20975] b4f76ecc9e Ignore MAP_VARIABLE in tst-mman-consts.py 7c32cb7dd8 gmon: Revert addition of tunables to the manual a908c18d47 gmon: Revert addition of tunables to preserve GLIBC_PRIVATE ABI ff3a71ec1f gmon: fix memory corruption issues [BZ# 30101] d230623264 gmon: improve mcount overflow handling [BZ# 27576] 5d750495db gmon: Fix allocated buffer overflow (bug 29444) 78ab913eab posix: Fix system blocks SIGCHLD erroneously [BZ #30163] 9cc2f41e52 x86_64: Fix asm constraints in feraiseexcept (bug 30305) 97ad4c64b9 gshadow: Matching sgetsgent, sgetsgent_r ERANGE handling (bug 30151) 1d63573f81 stdio-common: tests: don't double-define _FORTIFY_SOURCE 590d0e089b elf: Restore ldconfig libc6 implicit soname logic [BZ #30125] 790e504a17 stdlib: Undo post review change to 16adc58e73f3 [BZ #27749] (From OE-Core rev: 8b0928acc22596614bc8a87ce57813cfc87c57de) 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.