a04b0eaa38
Brings these changes * 1d5750b9 fix swprintf handling of nul character in output * 0e523480 in printf, use ferror macro rather than directly inspecting flags bit * 868c9643 remove wide printf dependency on ugly hack in vfprintf * 3a051769 fix (normal, narrow) printf erroneously processing %n after output errors * 0440ed69 fix wide printf continuation after output or encoding errors * d055e6a4 fix wide printf forms ignoring width for %lc format specifier * b6811019 poll: fix misuse of timespec type on 32-bit archs without poll syscall * 8949da7a select: fix 64-bit timeout truncation on pre-time64 kernels * 3281047c dup3: don't set FD_CLOEXEC on failure on kernels without dup3 syscall * c99b7daa fix dup3 ignoring all flags but O_CLOEXEC on archs with SYS_dup2 syscall * fb7fb5e4 fix pipe2 silently ignoring unknown flags on old kernels * b1dfb734 getservbyport_r: fix wrong result if getnameinfo fails with EAI_OVERFLOW * 595416b1 getservbyport_r: fix out-of-bounds buffer read * 1a708ece getifaddrs: fix UB via taking address of null pointer union dereference * c499c108 accept4: don't fall back to accept if we got unknown flags * 523d9b96 fix potential read past end of buffer in getnameinfo host name lookup * d0b7f976 dns: fix workaround for systems defaulting to ipv6-only sockets * bec42ef3 dns: handle early eof in tcp fallback * 9b132e55 prevent CNAME/PTR parsing from reading data past the response end * 12590c8b fix out-of-bounds reads in __dns_parse * bc695a5a fix incorrect unit for CPU_SETSIZE macro (From OE-Core rev: bb591e83e3d203d60d59a36f1ff0b2ce437dc7a2) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@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.