d32aa383f4
Brings in below changes * 499a601796 Default to --with-default-link=no (bug 25812) * 70f1eecdc1 scripts: Add glibcelf.py module * d3feff2232 m68k: Handle fewer relocations for RTLD_BOOTSTRAP (#BZ29071) * 68d3a9a696 nptl: Fix pthread_cancel cancelhandling atomic operations * 8e8d46d598 mips: Fix mips64n32 64 bit time_t stat support (BZ#29069) * bd415684df hurd: Fix arbitrary error code * ba9c42ac0e nptl: Handle spurious EINTR when thread cancellation is disabled (BZ#29029) * 6583d53445 S390: Add new s390 platform z16. * cc9a4a664f elf: Fix memory leak in _dl_find_object_update (bug 29062) * db03235895 NEWS: Move PLT tracking slowdown to glibc 2.35. * 9be62976af hppa: Use END instead of PSEUDO_END in swapcontext.S * 01d5214bb4 hppa: Implement swapcontext in assembler (bug 28960) * 123bd1ec66 nss: Protect against errno changes in function lookup (bug 28953) * c54c5cd8e3 nss: Do not mention NSS test modules in <gnu/lib-names.h> * 3149f47b80 io: Add fsync call in tst-stat * e30c1c73da nptl: Fix cleanups for stack grows up [BZ# 28899] * ca0570fee3 hppa: Fix warnings from _dl_lookup_address * d82d9cdff4 hppa: Revise gettext trampoline design * 2631d3b3a6 hppa: Fix swapcontext * 1f77081178 Fix elf/tst-audit2 on hppa * c60e6a458b hppa: Fix bind-now audit (BZ #28857) * 90797f4972 localedef: Handle symbolic links when generating locale-archive * 732dd3a63d localedata: Do not generate output if warnings were present. * 3feecd8001 localedef: Update LC_MONETARY handling (Bug 28845) * a787325e83 NEWS: Add a bug fix entry for BZ #28688 * 264ad5d7d6 resolv: Fix tst-resolv tests for 2.35 ABIs and later * e247a3b118 elf: Replace tst-audit24bmod2.so with tst-audit24bmod2 * 1dd783fafd elf: Check invalid hole in PT_LOAD segments [BZ #28838] * 3226ffde07 NEWS: Add a bug fix entry for BZ #28896 * 676f85759c x86: Fix TEST_NAME to make it a string in tst-strncmp-rtm.c * d001088e22 x86: Test wcscmp RTM in the wcsncmp overflow case [BZ #28896] * fd412fff6d x86: Fallback {str|wcs}cmp RTM in the ncmp overflow case [BZ #28896] * a30807b7db string: Add a testcase for wcsncmp with SIZE_MAX [BZ #28755] * f055faf801 linux: Use socket-constants-time64.h on tst-socket-timestamp-compat * 491f2ef1f0 linux: fix accuracy of get_nprocs and get_nprocs_conf [BZ #28865] (From OE-Core rev: f199c89a9b94ba371d3c6b9a9b5afe06d9a7fb9b) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com> 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
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.