12abaeb0fe
Below commits on glibc-2.40 stable branch are updated. efb710034e linux: sparc: Fix clone for LEON/sparcv8 (BZ 31394) 2344580243 Mitigation for "clone on sparc might fail with -EFAULT for no valid reason" (bz 31394) 3a34851103 elf: Change ldconfig auxcache magic number (bug 32231) 85e5850f2f Make tst-strtod-underflow type-generic 5c06c6e0b5 libio: Set _vtable_offset before calling _IO_link_in [BZ #32148] cc256952ec Add tests of more strtod special cases 8f40dfbe2a Add more tests of strtod end pointer 4a9b6cdc88 Make tst-strtod2 and tst-strtod5 type-generic 5a10d05c39 powerpc64le: Build new strtod tests with long double ABI flags (bug 32145) c4cc72d2ef Do not set errno for overflowing NaN payload in strtod/nan (bug 32045) ad93c2047d Improve NaN payload testing cac10d88c6 Make __strtod_internal tests type-generic d0c1792ad2 Fix strtod subnormal rounding (bug 30220) e06153665f More thoroughly test underflow / errno in tst-strtod-round 9bc76c7ca4 Test errno setting on strtod overflow in tst-strtod-round 61b6464f8d Add tests of fread 77018fd9f9 stdio-common: Add new test for fdopen Testresults: After update |Before update |Difference PASS: 5005 |PASS: 5002 |PASS: 3 FAIL: 166 |FAIL: 167 |FAIL: -1 XPASS: 4 |XPASS: 4 |XPASS: 0 XFAIL: 16 |XFAIL: 16 |XFAIL: 0 UNSUPPORTED: 229|UNSUPPORTED: 229|UNSUPPORTED: 0 (From OE-Core rev: 3ae9098c8c4cdc635cc449190f340dc20d6e7318) Signed-off-by: Deepthi Hemraj <Deepthi.Hemraj@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.