Wang Mingyu 0184420b15 python3: upgrade 3.11.4 -> 3.11.5
Changelog:
============
-gh-104432: Fix potential unaligned memory access on C APIs involving returned
 sequences of char * pointers within the grp and socket modules. These were
 revealed using a -fsaniziter=alignment build on ARM macOS.
-gh-77377: Ensure that multiprocessing synchronization objects created in a fork
 context are not sent to a different process created in a spawn context.
 This changes a segfault into an actionable RuntimeError in the parent process.
-gh-106092: Fix a segmentation fault caused by a use-after-free bug in frame_dealloc when the trashcan delays the deallocation of a PyFrameObject.
-gh-106719: No longer suppress arbitrary errors in the __annotations__ getter and setter in the type and module types.
-gh-106723: Propagate frozen_modules to multiprocessing spawned process interpreters.
-gh-105979: Fix crash in _imp.get_frozen_object() due to improper exception handling.
-gh-105840: Fix possible crashes when specializing function calls with too many __defaults__.
-gh-105588: Fix an issue that could result in crashes when compiling malformed ast nodes.
-gh-105375: Fix bugs in the builtins module where exceptions could end up being overwritten.
-gh-105375: Fix bug in the compiler where an exception could end up being overwritten.
-gh-105375: Improve error handling in PyUnicode_BuildEncodingMap() where an exception could end up being overwritten.
-gh-105235: Prevent out-of-bounds memory access during mmap.find() calls.
--gh-101006: Improve error handling when read marshal data.

(From OE-Core rev: 70df63c2fe59ab781152b6981caf0828ececc54e)

Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2023-09-02 18:23:06 +01:00
2023-09-02 18:23:06 +01:00
2021-07-19 18:07:21 +01:00

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/):

BitBake (files in bitbake/):

Documentation (files in documentation/):

meta-yocto (files in meta-poky/, meta-yocto-bsp/):

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.

CII Best Practices

Description
No description provided
Readme 251 MiB