a2443e25a6
git log --oneline d2097651cc57834dbfcaa102ddfacae0d86cfb66..e34453cd6a8c592c325756ff3c7ac0afd3975cb4 e34453cd6a (HEAD, origin/release/2.42/master) AArch64: Fix SVE powf routine [BZ #33299] e87844ec42 i386: Also add GLIBC_ABI_GNU2_TLS version [BZ #33129] 7a8f3c6ee4 x86-64: Add GLIBC_ABI_DT_X86_64_PLT [BZ #33212] 3970785beb x86-64: Add GLIBC_ABI_GNU2_TLS version [BZ #33129] d0f72b96f2 i386: Add GLIBC_ABI_GNU_TLS version [BZ #33221] 8dbaecbe92 Use TLS initial-exec model for __libc_tsd_CTYPE_* thread variables [BZ #33234] d7274d718e malloc: Fix checking for small negative values of tcache_key a96a82c4a5 malloc: Make sure tcache_key is odd enough c491dabd8a malloc: Fix MAX_TCACHE_SMALL_SIZE 8a726b6304 malloc: Remove redundant NULL check c5476b7907 hurd: support: Fix running SGID tests e5754399b5 Revert "tst-freopen4-main.c: Call support_capture_subprocess with chroot" c090b0cb1c tst-env-setuid: Delete LD_DEBUG_OUTPUT output 41a77b78cf tst-freopen4-main.c: Call support_capture_subprocess with chroot 9ec7a532ff tst-fopen-threaded.c: Delete temporary file 9d5bf9c17d Delete temporary files in support_subprocess b38f3f60d5 nptl: Fix SYSCALL_CANCEL for return values larger than INT_MAX (BZ 33245) 5e298d2d93 elf: Handle ld.so with LOAD segment gaps in _dl_find_object (bug 31943) 2fadee5301 elf: Extract rtld_setup_phdr function from dl_main fd18059c0f stdlib: resolve a double lock init issue after fork [BZ #32994] bc13db7393 inet-fortified: fix namespace violation (bug 33227) 3ec4dd77f6 NEWS: add new section bdea6c3719 Replace advisories directory with pointer file Testing Results: Before After Diff PASS 5842 5855 +13 XPASS 4 4 0 FAIL 868 859 -9 XFAIL 16 16 0 UNSUPPORTED 396 396 0 Testcases changes testcase-name before after elf/check-dt-x86-64-plt(new) - PASS elf/check-gnu2-tls(new) - PASS elf/tst-link-map-contiguous-ldso(new) - PASS elf/tst-link-map-contiguous-libc(new) - PASS malloc/tst-malloc_info-malloc-hugetlb1 FAIL PASS nptl/tst-thread-affinity-pthread FAIL PASS resolv/tst-resolv-aliases FAIL PASS stdio-common/tst-printf-format-d-llong FAIL PASS stdio-common/tst-printf-format-sn-ushort FAIL PASS stdio-common/tst-printf-format-vs-char FAIL PASS stdio-common/tst-printf-format-vd-ullong FAIL PASS string/test-strcmp FAIL PASS string/tst-cmp FAIL PASS (From OE-Core rev: e4d73b2021535473f1f2970edf53d0105f10ba5a) Signed-off-by: Deepesh Varatharajan <Deepesh.Varatharajan@windriver.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@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
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.