mirror of
git://git.yoctoproject.org/poky.git
synced 2025-07-19 21:09:03 +02:00
Compare commits
31 Commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
9b96fdbb0c | ||
|
|
81c9c4f6d4 | ||
|
|
51d1210367 | ||
|
|
43909a9870 | ||
|
|
185a87256e | ||
|
|
22f3616aad | ||
|
|
58776612f0 | ||
|
|
62689ff1fb | ||
|
|
528b36636b | ||
|
|
5f6a1c9838 | ||
|
|
17b2110721 | ||
|
|
542eec1b1c | ||
|
|
a472092f33 | ||
|
|
3408d70d2c | ||
|
|
8df460977d | ||
|
|
fdf0ab1370 | ||
|
|
5c4cf4b573 | ||
|
|
e5577538c3 | ||
|
|
90e4af3eff | ||
|
|
15a7d7b881 | ||
|
|
39cbc37918 | ||
|
|
9f9e7bbace | ||
|
|
539ce63c81 | ||
|
|
43d807650a | ||
|
|
949c0bb2f5 | ||
|
|
0c32303252 | ||
|
|
ecacb6015a | ||
|
|
0990fceebe | ||
|
|
6b2bc1e4cb | ||
|
|
5ec826fa2e | ||
|
|
a287584563 |
|
|
@ -44,7 +44,7 @@ following requirements:
|
|||
much more will help to run multiple builds and increase
|
||||
performance by reusing build artifacts.
|
||||
|
||||
- At least &MIN_RAM; Gbytes of RAM, though a modern modern build host with as
|
||||
- At least &MIN_RAM; Gbytes of RAM, though a modern build host with as
|
||||
much RAM and as many CPU cores as possible is strongly recommended to
|
||||
maximize build performance.
|
||||
|
||||
|
|
|
|||
|
|
@ -166,7 +166,7 @@ section.
|
|||
BSPs, which are maintained in their own layers or in layers designed
|
||||
to contain several BSPs. To get an idea of machine support through
|
||||
BSP layers, you can look at the
|
||||
:yocto_dl:`index of machines </releases/yocto/yocto-&DISTRO;/machines>`
|
||||
:yocto_dl:`index of machines </releases/yocto/&DISTRO_REL_LATEST_TAG;/machines>`
|
||||
for the release.
|
||||
|
||||
#. *Optionally Clone the meta-intel BSP Layer:* If your hardware is
|
||||
|
|
|
|||
|
|
@ -111,6 +111,9 @@ extlinks = {
|
|||
'wikipedia': ('https://en.wikipedia.org/wiki/%s', None),
|
||||
}
|
||||
|
||||
# To be able to use :manpage:`<something>` in the docs.
|
||||
manpages_url = 'https://manpages.debian.org/{path}'
|
||||
|
||||
# Intersphinx config to use cross reference with BitBake user manual
|
||||
intersphinx_mapping = {
|
||||
'bitbake': ('https://docs.yoctoproject.org/bitbake/' + bitbake_version, None)
|
||||
|
|
|
|||
|
|
@ -75,7 +75,7 @@ available. Follow these general steps to run QEMU:
|
|||
your :term:`Build Directory`.
|
||||
|
||||
- If you have not built an image, you can go to the
|
||||
:yocto_dl:`machines/qemu </releases/yocto/yocto-&DISTRO;/machines/qemu/>` area and download a
|
||||
:yocto_dl:`machines/qemu </releases/yocto/&DISTRO_REL_LATEST_TAG;/machines/qemu/>` area and download a
|
||||
pre-built image that matches your architecture and can be run on
|
||||
QEMU.
|
||||
|
||||
|
|
|
|||
|
|
@ -615,7 +615,7 @@ Accessing Source Archives
|
|||
The Yocto Project also provides source archives of its releases, which
|
||||
are available on :yocto_dl:`/releases/yocto/`. Then, choose the subdirectory
|
||||
containing the release you wish to use, for example
|
||||
:yocto_dl:`yocto-&DISTRO; </releases/yocto/yocto-&DISTRO;/>`.
|
||||
:yocto_dl:`&DISTRO_REL_LATEST_TAG; </releases/yocto/&DISTRO_REL_LATEST_TAG;/>`.
|
||||
|
||||
You will find there source archives of individual components (if you wish
|
||||
to use them individually), and of the corresponding Poky release bundling
|
||||
|
|
|
|||
|
|
@ -104,6 +104,13 @@ systemd changes
|
|||
``journald.conf`` to "persistent". The ``/var/log/journal`` directory is now
|
||||
used for logging instead of ``/run/log``.
|
||||
|
||||
- If ``pni-names`` is not in the :term:`DISTRO_FEATURES`, the `Predictable
|
||||
Network Interface names <https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/>`__
|
||||
systemd feature will now be disabled. Previously the feature was still
|
||||
enabled even if ``pni-names`` was not part of :term:`DISTRO_FEATURES`. Make
|
||||
sure to add the feature to :term:`DISTRO_FEATURES` if you want to keep this
|
||||
systemd behavior.
|
||||
|
||||
Multiconfig changes
|
||||
~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
|
|
@ -186,12 +193,22 @@ The support for having multiple Git revisions per URL in :term:`SRC_URI` was
|
|||
removed from BitBake, which means the following syntax is not supported
|
||||
anymore::
|
||||
|
||||
SRC_URI = "git://some.host/somepath;branch=branchX,branchY;name=nameX,nameY"
|
||||
SRC_URI = "git://some.host/somepath;bareclone=1;branch=branchX,branchY;name=nameX,nameY"
|
||||
SRCREV_nameX = "xxxxxxxxxxxxxxxxxxxx"
|
||||
SRCREV_nameY = "yyyyyyyyyyyyyyyyyyyy"
|
||||
|
||||
This was rarely used in the core repositories, and this removal simplifies the
|
||||
code logic in several places.
|
||||
This was rarely used in the core repositories because it would only ever make
|
||||
sense for bare clones (the ``bareclone=1`` :term:`SRC_URI` option) where recipes
|
||||
take care of the Git checkout. This removal simplifies the code logic in several
|
||||
places.
|
||||
|
||||
If one of your recipes is using this mechanism, you can split the code source
|
||||
fetching into two separate entries::
|
||||
|
||||
SRC_URI = "git://some.host/somepath;bareclone=1;branch=branchX;name=nameX \
|
||||
git://some.host/somepath;bareclone=1;branch=branchY;name=nameY"
|
||||
SRCREV_nameX = "xxxxxxxxxxxxxxxxxxxx"
|
||||
SRCREV_nameY = "yyyyyyyyyyyyyyyyyyyy"
|
||||
|
||||
Git fetcher: Branch parameter now required in :term:`SRC_URI`
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
|
@ -242,7 +259,7 @@ The following recipes have been removed in this release:
|
|||
:oe_git:`openembedded-core </openembedded-core>` or :oe_git:`meta-openembedded </meta-openembedded>`.
|
||||
|
||||
- ``blktool``: It was created in 2004 as an alternative to hdparm and never
|
||||
updated since (while :wikipedia:`hdparm <Hdparm>` remains in active.
|
||||
updated since (while :wikipedia:`hdparm <Hdparm>` remains active).
|
||||
|
||||
- ``cargo-c-native``: converted to a target recipe and renamed to ``cargo-c``.
|
||||
|
||||
|
|
|
|||
|
|
@ -14,4 +14,4 @@ Release 5.0 (scarthgap)
|
|||
release-notes-5.0.5
|
||||
release-notes-5.0.6
|
||||
release-notes-5.0.7
|
||||
|
||||
release-notes-5.0.8
|
||||
|
|
|
|||
|
|
@ -10,3 +10,4 @@ Release 5.1 (styhead)
|
|||
release-notes-5.1.1
|
||||
release-notes-5.1.2
|
||||
release-notes-5.1.3
|
||||
release-notes-5.1.4
|
||||
|
|
|
|||
226
documentation/migration-guides/release-notes-5.0.8.rst
Normal file
226
documentation/migration-guides/release-notes-5.0.8.rst
Normal file
|
|
@ -0,0 +1,226 @@
|
|||
.. SPDX-License-Identifier: CC-BY-SA-2.0-UK
|
||||
|
||||
Release notes for Yocto-5.0.8 (Scarthgap)
|
||||
-----------------------------------------
|
||||
|
||||
Security Fixes in Yocto-5.0.8
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
- binutils: Fix :cve_nist:`2025-0840`
|
||||
- curl: Ignore :cve_nist:`2025-0725`
|
||||
- elfutils: Fix :cve_nist:`2025-1352`, :cve_nist:`2025-1365` and :cve_nist:`2025-1372`
|
||||
- ffmpeg: Fix :cve_nist:`2024-35365`, :cve_nist:`2024-35369`, :cve_nist:`2024-36613`,
|
||||
:cve_nist:`2024-36616`, :cve_nist:`2024-36617`, :cve_nist:`2024-36618`, :cve_nist:`2024-36619`,
|
||||
:cve_nist:`2025-0518`, :cve_nist:`2025-22919`, :cve_nist:`2025-22921` and :cve_nist:`2025-25473`
|
||||
- glibc: Fix :cve_nist:`2025-0395`
|
||||
- gnutls: Fix :cve_nist:`2024-12243`
|
||||
- go: Fix :cve_nist:`2024-45336`, :cve_nist:`2024-45341` and :cve_nist:`2025-22866`
|
||||
- gstreamer1.0-rtsp-server: Fix :cve_nist:`2024-44331`
|
||||
- libcap: Fix :cve_nist:`2025-1390`
|
||||
- libtasn1: Fix :cve_nist:`2024-12133`
|
||||
- libxml2: Fix :cve_nist:`2024-56171` and :cve_nist:`2025-24928`
|
||||
- linux-yocto/6.6: Fix :cve_nist:`2024-36476`, :cve_nist:`2024-53179`, :cve_nist:`2024-56582`,
|
||||
:cve_nist:`2024-56703`, :cve_nist:`2024-57801`, :cve_nist:`2024-57802`, :cve_nist:`2024-57841`,
|
||||
:cve_nist:`2024-57882`, :cve_nist:`2024-57887`, :cve_nist:`2024-57890`, :cve_nist:`2024-57892`,
|
||||
:cve_nist:`2024-57895`, :cve_nist:`2024-57896`, :cve_nist:`2024-57900`, :cve_nist:`2024-57901`,
|
||||
:cve_nist:`2024-57902`, :cve_nist:`2024-57906`, :cve_nist:`2024-57907`, :cve_nist:`2024-57908`,
|
||||
:cve_nist:`2024-57910`, :cve_nist:`2024-57911`, :cve_nist:`2024-57912`, :cve_nist:`2024-57913`,
|
||||
:cve_nist:`2024-57916`, :cve_nist:`2024-57922`, :cve_nist:`2024-57925`, :cve_nist:`2024-57926`,
|
||||
:cve_nist:`2024-57933`, :cve_nist:`2024-57938`, :cve_nist:`2024-57939`, :cve_nist:`2024-57940`,
|
||||
:cve_nist:`2024-57949`, :cve_nist:`2024-57951`, :cve_nist:`2025-21631`, :cve_nist:`2025-21636`,
|
||||
:cve_nist:`2025-21637`, :cve_nist:`2025-21638`, :cve_nist:`2025-21639`, :cve_nist:`2025-21640`,
|
||||
:cve_nist:`2025-21642`, :cve_nist:`2025-21652`, :cve_nist:`2025-21658`, :cve_nist:`2025-21665`,
|
||||
:cve_nist:`2025-21666`, :cve_nist:`2025-21667`, :cve_nist:`2025-21669`, :cve_nist:`2025-21670`,
|
||||
:cve_nist:`2025-21671`, :cve_nist:`2025-21673`, :cve_nist:`2025-21674`, :cve_nist:`2025-21675`,
|
||||
:cve_nist:`2025-21676`, :cve_nist:`2025-21680`, :cve_nist:`2025-21681`, :cve_nist:`2025-21683`,
|
||||
:cve_nist:`2025-21684`, :cve_nist:`2025-21687`, :cve_nist:`2025-21689`, :cve_nist:`2025-21690`,
|
||||
:cve_nist:`2025-21692`, :cve_nist:`2025-21694`, :cve_nist:`2025-21697` and :cve_nist:`2025-21699`
|
||||
- openssh: Fix :cve_nist:`2025-26466`
|
||||
- openssl: Fix :cve_nist:`2024-9143`, :cve_nist:`2024-12797` and :cve_nist:`2024-13176`
|
||||
- pyhton3: Fix :cve_nist:`2024-12254` and :cve_nist:`2025-0938`
|
||||
- subversion: Ignore :cve_nist:`2024-45720`
|
||||
- u-boot: Fix :cve_nist:`2024-57254`, :cve_nist:`2024-57255`, :cve_nist:`2024-57256`,
|
||||
:cve_nist:`2024-57257`, :cve_nist:`2024-57258` and :cve_nist:`2024-57259`
|
||||
- vim: Fix :cve_nist:`2025-22134` and :cve_nist:`2025-24014`
|
||||
- xwayland: Fix :cve_nist:`2024-9632`, :cve_nist:`2025-26594`, :cve_nist:`2025-26595`,
|
||||
:cve_nist:`2025-26596`, :cve_nist:`2025-26597`, :cve_nist:`2025-26598`, :cve_nist:`2025-26599`,
|
||||
:cve_nist:`2025-26600` and :cve_nist:`2025-26601`
|
||||
|
||||
|
||||
Fixes in Yocto-5.0.8
|
||||
~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
- base-files: Drop /bin/sh dependency
|
||||
- bind: upgrade to 9.18.33
|
||||
- binutils: File name too long causing failure to open temporary head file in dlltool
|
||||
- binutils: stable 2.42 branch update
|
||||
- bitbake: bblayers/query: Fix using "removeprefix" string method
|
||||
- bitbake: bitbake-diffsigs: fix handling when finding only a single sigfile
|
||||
- bitbake: data_smart.py: clear expand_cache in _setvar_update_overridevars
|
||||
- bitbake: data_smart.py: remove unnecessary ? from __expand_var_regexp__
|
||||
- bitbake: data_smart.py: simple clean up
|
||||
- build-appliance-image: Update to scarthgap head revision
|
||||
- ccache.conf: Add include_file_ctime to sloppiness
|
||||
- cmake: apply parallel build settings to ptest tasks
|
||||
- contributor-guide/submit-changes: add policy on AI generated code
|
||||
- dev-manual/building: document the initramfs-framework recipe
|
||||
- devtool: ide-sdk recommend :term:`DEBUG_BUILD`
|
||||
- devtool: ide-sdk remove the plugin from eSDK installer
|
||||
- devtool: ide-sdk sort cmake preset
|
||||
- devtool: modify support debug-builds
|
||||
- docs: Add favicon for the documentation html
|
||||
- docs: Fix typo in standards.md
|
||||
- docs: Remove all mention of core-image-lsb
|
||||
- docs: vulnerabilities/classes: remove references to cve-check text format
|
||||
- files: Amend overlayfs unit descriptions with path information
|
||||
- files: overlayfs-create-dirs: Improve mount unit dependency
|
||||
- glibc: stable 2.39 branch updates
|
||||
- gnupg: upgrade to 2.4.5
|
||||
- go: upgrade 1.22.12
|
||||
- icu: remove host references in nativesdk to fix reproducibility
|
||||
- libtasn1: upgrade to 4.20.0
|
||||
- libxml2: upgrade to 2.12.10
|
||||
- linux-yocto/6.6: upgrade to v6.6.75
|
||||
- meta: Enable '-o pipefail' for the SDK installer
|
||||
- migration-guides: add release notes for 4.0.24, 4.0.25 and 5.0.7
|
||||
- oe-selftest: devtool ide-sdk use modify debug-build
|
||||
- oeqa/sdk/context: fix for gtk3 test failure during do_testsdk
|
||||
- oeqa/selftest/rust: skip on all MIPS platforms
|
||||
- openssl: upgrade to 3.2.4
|
||||
- pkg-config-native: pick additional search paths from $EXTRA_NATIVE_PKGCONFIG_PATH
|
||||
- poky.conf: add ubuntu2404 to :term:`SANITY_TESTED_DISTROS`
|
||||
- poky.conf: bump version for 5.0.8
|
||||
- ppp: Revert lock path to /var/lock
|
||||
- python3-setuptools-scm: respect GIT_CEILING_DIRECTORIES
|
||||
- python3: upgrade to 3.12.9
|
||||
- qemu: Do not define sched_attr with glibc >= 2.41
|
||||
- ref-manual/faq: add q&a on systemd as default
|
||||
- ref-manual: Add missing variable :term:`IMAGE_ROOTFS_MAXSIZE`
|
||||
- ref-manual: don't refer to poky-lsb
|
||||
- ref-manual: remove OE_IMPORTS
|
||||
- rust-common.bbclass: soft assignment for RUSTLIB path
|
||||
- rust: fix for rust multilib sdk configuration
|
||||
- rust: remove redundant cargo config file
|
||||
- scripts/install-buildtools: Update to 5.0.7
|
||||
- sdk-manual: extensible.rst: devtool ide-sdk improve
|
||||
- sdk-manual: extensible.rst: update devtool ide-sdk
|
||||
- selftest/rust: correctly form the PATH environment variable
|
||||
- systemd: add libpcre2 as :term:`RRECOMMENDS` if pcre2 is enabled
|
||||
- systemd: upgrade to 255.17
|
||||
- test-manual/ptest: link to common framework ptest classes
|
||||
- tzcode-native: Fix compiler setting from 2023d version
|
||||
- tzdata/tzcode-native: upgrade to 2025a
|
||||
- u-boot: kernel-fitimage: Fix dependency loop if :term:`UBOOT_SIGN_ENABLE` and UBOOT_ENV enabled
|
||||
- u-boot: kernel-fitimage: Restore FIT_SIGN_INDIVIDUAL="1" behavior
|
||||
- uboot-config: fix devtool modify with kernel-fitimage
|
||||
- vim: upgrade to 9.1.1043
|
||||
|
||||
|
||||
Known Issues in Yocto-5.0.8
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
- N/A
|
||||
|
||||
Contributors to Yocto-5.0.8
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
Thanks to the following people who contributed to this release:
|
||||
|
||||
- Adrian Freihofer
|
||||
- Aleksandar Nikolic
|
||||
- Alessio Cascone
|
||||
- Alexander Kanavin
|
||||
- Alexis Cellier
|
||||
- Antonin Godard
|
||||
- Archana Polampalli
|
||||
- Bruce Ashfield
|
||||
- Chen Qi
|
||||
- Deepesh Varatharajan
|
||||
- Divya Chellam
|
||||
- Enrico Jörns
|
||||
- Esben Haabendal
|
||||
- Etienne Cordonnier
|
||||
- Fabio Berton
|
||||
- Guðni Már Gilbert
|
||||
- Harish Sadineni
|
||||
- Hitendra Prajapati
|
||||
- Hongxu Jia
|
||||
- Jiaying Song
|
||||
- Joerg Schmidt
|
||||
- Johannes Schneider
|
||||
- Khem Raj
|
||||
- Lee Chee Yang
|
||||
- Marek Vasut
|
||||
- Marta Rybczynska
|
||||
- Moritz Haase
|
||||
- Oleksandr Hnatiuk
|
||||
- Pedro Ferreira
|
||||
- Peter Marko
|
||||
- Poonam Jadhav
|
||||
- Priyal Doshi
|
||||
- Ross Burton
|
||||
- Simon A. Eugster
|
||||
- Steve Sakoman
|
||||
- Vijay Anusuri
|
||||
- Wang Mingyu
|
||||
- Weisser, Pascal
|
||||
|
||||
|
||||
Repositories / Downloads for Yocto-5.0.8
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
poky
|
||||
|
||||
- Repository Location: :yocto_git:`/poky`
|
||||
- Branch: :yocto_git:`scarthgap </poky/log/?h=scarthgap>`
|
||||
- Tag: :yocto_git:`yocto-5.0.8 </poky/log/?h=yocto-5.0.8>`
|
||||
- Git Revision: :yocto_git:`dc4827b3660bc1a03a2bc3b0672615b50e9137ff </poky/commit/?id=dc4827b3660bc1a03a2bc3b0672615b50e9137ff>`
|
||||
- Release Artefact: poky-dc4827b3660bc1a03a2bc3b0672615b50e9137ff
|
||||
- sha: ace7264e16e18ed02ef0ad2935fa10b5fad2c4de38b2356f4192b38ef2184504
|
||||
- Download Locations:
|
||||
https://downloads.yoctoproject.org/releases/yocto/yocto-5.0.8/poky-dc4827b3660bc1a03a2bc3b0672615b50e9137ff.tar.bz2
|
||||
https://mirrors.kernel.org/yocto/yocto/yocto-5.0.8/poky-dc4827b3660bc1a03a2bc3b0672615b50e9137ff.tar.bz2
|
||||
|
||||
openembedded-core
|
||||
|
||||
- Repository Location: :oe_git:`/openembedded-core`
|
||||
- Branch: :oe_git:`scarthgap </openembedded-core/log/?h=scarthgap>`
|
||||
- Tag: :oe_git:`yocto-5.0.8 </openembedded-core/log/?h=yocto-5.0.8>`
|
||||
- Git Revision: :oe_git:`cd2b6080a4c0f2ed2c9939ec0b87763aef595048 </openembedded-core/commit/?id=cd2b6080a4c0f2ed2c9939ec0b87763aef595048>`
|
||||
- Release Artefact: oecore-cd2b6080a4c0f2ed2c9939ec0b87763aef595048
|
||||
- sha: 14c7cd5c62a96ceb9c2141164ea0f087fdbaed99ca3e9a722977a3f12d6381f6
|
||||
- Download Locations:
|
||||
https://downloads.yoctoproject.org/releases/yocto/yocto-5.0.8/oecore-cd2b6080a4c0f2ed2c9939ec0b87763aef595048.tar.bz2
|
||||
https://mirrors.kernel.org/yocto/yocto/yocto-5.0.8/oecore-cd2b6080a4c0f2ed2c9939ec0b87763aef595048.tar.bz2
|
||||
|
||||
meta-mingw
|
||||
|
||||
- Repository Location: :yocto_git:`/meta-mingw`
|
||||
- Branch: :yocto_git:`scarthgap </meta-mingw/log/?h=scarthgap>`
|
||||
- Tag: :yocto_git:`yocto-5.0.8 </meta-mingw/log/?h=yocto-5.0.8>`
|
||||
- Git Revision: :yocto_git:`bd9fef71ec005be3c3a6d7f8b99d8116daf70c4f </meta-mingw/commit/?id=bd9fef71ec005be3c3a6d7f8b99d8116daf70c4f>`
|
||||
- Release Artefact: meta-mingw-bd9fef71ec005be3c3a6d7f8b99d8116daf70c4f
|
||||
- sha: ab073def6487f237ac125d239b3739bf02415270959546b6b287778664f0ae65
|
||||
- Download Locations:
|
||||
https://downloads.yoctoproject.org/releases/yocto/yocto-5.0.8/meta-mingw-bd9fef71ec005be3c3a6d7f8b99d8116daf70c4f.tar.bz2
|
||||
https://mirrors.kernel.org/yocto/yocto/yocto-5.0.8/meta-mingw-bd9fef71ec005be3c3a6d7f8b99d8116daf70c4f.tar.bz2
|
||||
|
||||
bitbake
|
||||
|
||||
- Repository Location: :oe_git:`/bitbake`
|
||||
- Branch: :oe_git:`2.8 </bitbake/log/?h=2.8>`
|
||||
- Tag: :oe_git:`yocto-5.0.8 </bitbake/log/?h=yocto-5.0.8>`
|
||||
- Git Revision: :oe_git:`7375d32e8c1af20c51abec4eb3b072b4ca58b239 </bitbake/commit/?id=7375d32e8c1af20c51abec4eb3b072b4ca58b239>`
|
||||
- Release Artefact: bitbake-7375d32e8c1af20c51abec4eb3b072b4ca58b239
|
||||
- sha: 13dffbc162c5b6e2c95fa72936a430b9a542d52d81d502a5d0afc592fbf4a16b
|
||||
- Download Locations:
|
||||
https://downloads.yoctoproject.org/releases/yocto/yocto-5.0.8/bitbake-7375d32e8c1af20c51abec4eb3b072b4ca58b239.tar.bz2
|
||||
https://mirrors.kernel.org/yocto/yocto/yocto-5.0.8/bitbake-7375d32e8c1af20c51abec4eb3b072b4ca58b239.tar.bz2
|
||||
|
||||
yocto-docs
|
||||
|
||||
- Repository Location: :yocto_git:`/yocto-docs`
|
||||
- Branch: :yocto_git:`scarthgap </yocto-docs/log/?h=scarthgap>`
|
||||
- Tag: :yocto_git:`yocto-5.0.8 </yocto-docs/log/?h=yocto-5.0.8>`
|
||||
- Git Revision: :yocto_git:`7d3cce5b962ca9f73b29affceb7ebc6710627739 </yocto-docs/commit/?id=7d3cce5b962ca9f73b29affceb7ebc6710627739>`
|
||||
|
||||
137
documentation/migration-guides/release-notes-5.1.4.rst
Normal file
137
documentation/migration-guides/release-notes-5.1.4.rst
Normal file
|
|
@ -0,0 +1,137 @@
|
|||
Release notes for Yocto-5.1.4 (Styhead)
|
||||
---------------------------------------
|
||||
|
||||
Security Fixes in Yocto-5.1.4
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
- binutils: Fix :cve_nist:`2025-0840`
|
||||
- grub: Fix :cve_nist:`2024-45774`, :cve_nist:`2024-45775`, :cve_nist:`2024-45776`,
|
||||
:cve_nist:`2024-45777`, :cve_nist:`2024-45778`, :cve_nist:`2024-45779`, :cve_nist:`2024-45780`,
|
||||
:cve_nist:`2024-45781`, :cve_nist:`2024-45782`, :cve_nist:`2024-45783`, :cve_nist:`2024-56737`,
|
||||
:cve_nist:`2025-0622`, :cve_nist:`2025-0624`, :cve_nist:`2025-0677`, :cve_nist:`2025-0678`,
|
||||
:cve_nist:`2025-0684`, :cve_nist:`2025-0685`, :cve_nist:`2025-0686`, :cve_nist:`2025-0689`,
|
||||
:cve_nist:`2025-0690`, :cve_nist:`2025-1118` and :cve_nist:`2025-1125`
|
||||
- libtasn1: fix :cve_nist:`2024-12133`
|
||||
- libxml2: fix :cve_nist:`2024-56171`, :cve_nist:`2025-24928` and :cve_nist:`2025-27113`
|
||||
- openssh: Fix :cve_nist:`2025-26465` and :cve_nist:`2025-26466`
|
||||
- puzzles: Ignore :cve_nist:`2024-13769`, :cve_nist:`2024-13770` and :cve_nist:`2025-0837`
|
||||
- subversion: Ignore :cve_nist:`2024-45720`
|
||||
- xserver-xorg: Fix :cve_nist:`2025-26594`, :cve_nist:`2025-26595`, :cve_nist:`2025-26596`,
|
||||
:cve_nist:`2025-26597`, :cve_nist:`2025-26598`, :cve_nist:`2025-26599`, :cve_nist:`2025-26600`
|
||||
and :cve_nist:`2025-26601`
|
||||
- xwayland: Fix :cve_nist:`2025-26594`, :cve_nist:`2025-26595`, :cve_nist:`2025-26596`,
|
||||
:cve_nist:`2025-26597`, :cve_nist:`2025-26598`, :cve_nist:`2025-26599`, :cve_nist:`2025-26600`
|
||||
and :cve_nist:`2025-26601`
|
||||
|
||||
|
||||
Fixes in Yocto-5.1.4
|
||||
~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
- bitbake: event/utils: Avoid deadlock from lock_timeout() and recursive events
|
||||
- bitbake: utils: Add signal blocking for lock_timeout
|
||||
- bitbake: utils: Print information about lock issue before exiting
|
||||
- bitbake: utils: Tweak lock_timeout logic
|
||||
- build-appliance-image: Update to styhead head revision
|
||||
- docs: Remove all mention of core-image-lsb
|
||||
- grub: backport strlcpy function
|
||||
- grub: drop obsolete CVE statuses
|
||||
- icu: Adjust ICU_DATA_DIR path on big endian targets
|
||||
- libtasn1: upgrade to 4.20.0
|
||||
- libxml2: upgrade to 2.13.6
|
||||
- migration-guides: add release notes for 4.0.25 and 5.1.3
|
||||
- poky.conf: bump version for 5.1.4
|
||||
- ref-manual: Add missing variable :term:`IMAGE_ROOTFS_MAXSIZE`
|
||||
- ref-manual: don't refer to poky-lsb
|
||||
- ref-manual: remove OE_IMPORTS
|
||||
- tzcode-native: Fix compiler setting from 2023d version
|
||||
- tzdata/tzcode-native: upgrade to 2025a
|
||||
- vulnerabilities/classes: remove references to cve-check text format
|
||||
- xserver-xf86-config: add a configuration fragment to disable screen blanking
|
||||
- xserver-xf86-config: remove obsolete configuration files
|
||||
- xserver-xorg: upgrade to 21.1.16
|
||||
- xwayland: upgrade to 21.1.6
|
||||
|
||||
|
||||
Known Issues in Yocto-5.1.4
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
- NA
|
||||
|
||||
Contributors to Yocto-5.1.4
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
|
||||
Thanks to the following people who contributed to this release:
|
||||
|
||||
- Alessio Cascone
|
||||
- Lee Chee Yang
|
||||
- Makarios Christakis
|
||||
- Marta Rybczynska
|
||||
- Peter Marko
|
||||
- Priyal Doshi
|
||||
- Richard Purdie
|
||||
- Ross Burton
|
||||
- Steve Sakoman
|
||||
- Vijay Anusuri
|
||||
- Wang Mingyu
|
||||
- Weisser, Pascal
|
||||
|
||||
|
||||
Repositories / Downloads for Yocto-5.1.4
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
poky
|
||||
|
||||
- Repository Location: :yocto_git:`/poky`
|
||||
- Branch: :yocto_git:`styhead </poky/log/?h=styhead>`
|
||||
- Tag: :yocto_git:`yocto-5.1.4 </poky/log/?h=yocto-5.1.4>`
|
||||
- Git Revision: :yocto_git:`70dc28ac287bf35541270cae1d99130a0f6b7b5f </poky/commit/?id=70dc28ac287bf35541270cae1d99130a0f6b7b5f>`
|
||||
- Release Artefact: poky-70dc28ac287bf35541270cae1d99130a0f6b7b5f
|
||||
- sha: 63f1d3d47a28bd9b41c89db6e1f2657c04233a00d10210795e766c0bc265d766
|
||||
- Download Locations:
|
||||
https://downloads.yoctoproject.org/releases/yocto/yocto-5.1.4/poky-70dc28ac287bf35541270cae1d99130a0f6b7b5f.tar.bz2
|
||||
https://mirrors.kernel.org/yocto/yocto/yocto-5.1.4/poky-70dc28ac287bf35541270cae1d99130a0f6b7b5f.tar.bz2
|
||||
|
||||
openembedded-core
|
||||
|
||||
- Repository Location: :oe_git:`/openembedded-core`
|
||||
- Branch: :oe_git:`styhead </openembedded-core/log/?h=styhead>`
|
||||
- Tag: :oe_git:`yocto-5.1.4 </openembedded-core/log/?h=yocto-5.1.4>`
|
||||
- Git Revision: :oe_git:`2d94f4b8a852dc761f89e5106347e239382df5fb </openembedded-core/commit/?id=2d94f4b8a852dc761f89e5106347e239382df5fb>`
|
||||
- Release Artefact: oecore-2d94f4b8a852dc761f89e5106347e239382df5fb
|
||||
- sha: 344ac23f814c049d69b06cee42c43b7b422506ce84397406caef09becb2555bf
|
||||
- Download Locations:
|
||||
https://downloads.yoctoproject.org/releases/yocto/yocto-5.1.4/oecore-2d94f4b8a852dc761f89e5106347e239382df5fb.tar.bz2
|
||||
https://mirrors.kernel.org/yocto/yocto/yocto-5.1.4/oecore-2d94f4b8a852dc761f89e5106347e239382df5fb.tar.bz2
|
||||
|
||||
meta-mingw
|
||||
|
||||
- Repository Location: :yocto_git:`/meta-mingw`
|
||||
- Branch: :yocto_git:`styhead </meta-mingw/log/?h=styhead>`
|
||||
- Tag: :yocto_git:`yocto-5.1.4 </meta-mingw/log/?h=yocto-5.1.4>`
|
||||
- Git Revision: :yocto_git:`77fe18d4f8ec34501045c5d92ce7e13b1bd129e9 </meta-mingw/commit/?id=77fe18d4f8ec34501045c5d92ce7e13b1bd129e9>`
|
||||
- Release Artefact: meta-mingw-77fe18d4f8ec34501045c5d92ce7e13b1bd129e9
|
||||
- sha: 4c7f8100a3675d9863e51825def3df5b263ffc81cd57bae26eedbc156d771534
|
||||
- Download Locations:
|
||||
https://downloads.yoctoproject.org/releases/yocto/yocto-5.1.4/meta-mingw-77fe18d4f8ec34501045c5d92ce7e13b1bd129e9.tar.bz2
|
||||
https://mirrors.kernel.org/yocto/yocto/yocto-5.1.4/meta-mingw-77fe18d4f8ec34501045c5d92ce7e13b1bd129e9.tar.bz2
|
||||
|
||||
bitbake
|
||||
|
||||
- Repository Location: :oe_git:`/bitbake`
|
||||
- Branch: :oe_git:`2.10 </bitbake/log/?h=2.10>`
|
||||
- Tag: :oe_git:`yocto-5.1.4 </bitbake/log/?h=yocto-5.1.4>`
|
||||
- Git Revision: :oe_git:`82b9f42126983579da03bdbb4e3ebf07346118a7 </bitbake/commit/?id=82b9f42126983579da03bdbb4e3ebf07346118a7>`
|
||||
- Release Artefact: bitbake-82b9f42126983579da03bdbb4e3ebf07346118a7
|
||||
- sha: 209d62c5262f2287af60e7fe2343c29ab25b5088de4da71de89016e75900285a
|
||||
- Download Locations:
|
||||
https://downloads.yoctoproject.org/releases/yocto/yocto-5.1.4/bitbake-82b9f42126983579da03bdbb4e3ebf07346118a7.tar.bz2
|
||||
https://mirrors.kernel.org/yocto/yocto/yocto-5.1.4/bitbake-82b9f42126983579da03bdbb4e3ebf07346118a7.tar.bz2
|
||||
|
||||
yocto-docs
|
||||
|
||||
- Repository Location: :yocto_git:`/yocto-docs`
|
||||
- Branch: :yocto_git:`styhead </yocto-docs/log/?h=styhead>`
|
||||
- Tag: :yocto_git:`yocto-5.1.4 </yocto-docs/log/?h=yocto-5.1.4>`
|
||||
- Git Revision: :yocto_git:`f0324b8f14881227336f84325cdebd0518e17796 </yocto-docs/commit/?id=f0324b8f14881227336f84325cdebd0518e17796>`
|
||||
|
||||
|
|
@ -44,11 +44,10 @@ New Features / Enhancements in |yocto-ver|
|
|||
uses.
|
||||
|
||||
- The :term:`GRUB_MKIMAGE_OPTS` can be used to control the flags to the
|
||||
``grub-mkimage`` command in the context of the Grub recipe (``grub-efi``).
|
||||
``grub-mkimage`` command in the context of the GRUB recipe (``grub-efi``).
|
||||
|
||||
- The :term:`SPDX_PACKAGE_VERSION` variable controls the package version as
|
||||
seen in the SPDX 3.0 JSON output (``software_packageVersion``). The default
|
||||
value for this variable is :term:`PV`.
|
||||
seen in the SPDX 3.0 JSON output (``software_packageVersion``).
|
||||
|
||||
- Kernel-related changes:
|
||||
|
||||
|
|
@ -345,8 +344,6 @@ New Features / Enhancements in |yocto-ver|
|
|||
- ``wget``: increase timeout to 100s from 30s to match CDN worst
|
||||
response time.
|
||||
|
||||
- ``wget``: Support setting :term:`PV` in :term:`SRC_URI`.
|
||||
|
||||
- Add support for fast initial shallow fetch. The fetcher will prefer an
|
||||
initial shallow clone, but will re-utilize an existing bare clone if
|
||||
there is one. If the remote server does not allow shallow fetches, the
|
||||
|
|
@ -450,6 +447,10 @@ New Features / Enhancements in |yocto-ver|
|
|||
with a matching hash and path, it will be linked, otherwise a new File
|
||||
element will be created.
|
||||
|
||||
- The output of :ref:`devtool upgrade-status
|
||||
<ref-manual/devtool-reference:Checking on the Upgrade Status of a Recipe>`
|
||||
is now sorted by recipe name.
|
||||
|
||||
- Patchtest-related changes:
|
||||
|
||||
- Refactor pattern definitions in a ``patterns`` module.
|
||||
|
|
@ -522,9 +523,10 @@ New Features / Enhancements in |yocto-ver|
|
|||
``${libdir}`` if the ``set-time-epoch`` :term:`PACKAGECONFIG` config is
|
||||
set.
|
||||
|
||||
- really disable Predictable Network Interface names if the ``pni-names``
|
||||
feature is not part of :term:`DISTRO_FEATURES`. Previously it was only
|
||||
really disable for QEMU machines.
|
||||
- really disable `Predictable Network Interface names
|
||||
<https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/>`__
|
||||
if the ``pni-names`` feature is not part of :term:`DISTRO_FEATURES`.
|
||||
Previously it was only really disabled for QEMU machines.
|
||||
|
||||
- split ``networkd`` into its own package named ``systemd-networkd``.
|
||||
|
||||
|
|
@ -808,7 +810,7 @@ The following CVEs have been fixed:
|
|||
* - ``curl``
|
||||
- :cve_nist:`2024-8096`, :cve_nist:`2024-9681`, :cve_nist:`2024-11053`, :cve_nist:`2025-0167`, :cve_nist:`2025-0665`, :cve_nist:`2025-0725`
|
||||
* - ``expat``
|
||||
- :cve_nist:`2024-50602`, :cve_nist:`2024-8176`
|
||||
- :cve_nist:`2024-8176`, :cve_nist:`2024-50602`
|
||||
* - ``ghostscript``
|
||||
- :cve_nist:`2024-46951`, :cve_nist:`2024-46952`, :cve_nist:`2024-46953`, :cve_nist:`2024-46954`, :cve_nist:`2024-46955`, :cve_nist:`2024-46956`
|
||||
* - ``gnutls``
|
||||
|
|
@ -816,23 +818,29 @@ The following CVEs have been fixed:
|
|||
* - ``go``
|
||||
- :cve_nist:`2024-34155`, :cve_nist:`2024-34156`, :cve_nist:`2024-34158`, :cve_nist:`2024-45336`, :cve_nist:`2024-45341`, :cve_nist:`2025-22866`, :cve_nist:`2025-22870`
|
||||
* - ``grub``
|
||||
- :cve_nist:`2024-45781`, :cve_nist:`2024-45782`, :cve_nist:`2024-56737`, :cve_nist:`2024-45780`, :cve_nist:`2024-45783`, :cve_nist:`2025-0624`, :cve_nist:`2024-45774`, :cve_nist:`2024-45775`, :cve_nist:`2025-0622`, :cve_nist:`2024-45776`, :cve_nist:`2024-45777`, :cve_nist:`2025-0690`, :cve_nist:`2025-1118`, :cve_nist:`2024-45778`, :cve_nist:`2024-45779`, :cve_nist:`2025-0677`, :cve_nist:`2025-0684`, :cve_nist:`2025-0685`, :cve_nist:`2025-0686`, :cve_nist:`2025-0689`, :cve_nist:`2025-0678`, :cve_nist:`2025-1125`
|
||||
- :cve_nist:`2024-45774`, :cve_nist:`2024-45775`, :cve_nist:`2024-45776`, :cve_nist:`2024-45777`, :cve_nist:`2024-45778`, :cve_nist:`2024-45779`, :cve_nist:`2024-45780`, :cve_nist:`2024-45781`, :cve_nist:`2024-45782`, :cve_nist:`2024-45783`, :cve_nist:`2024-56737`, :cve_nist:`2025-0622`, :cve_nist:`2025-0624`, :cve_nist:`2025-0677`, :cve_nist:`2025-0678`, :cve_nist:`2025-0684`, :cve_nist:`2025-0685`, :cve_nist:`2025-0686`, :cve_nist:`2025-0689`, :cve_nist:`2025-0690`, :cve_nist:`2025-1118`, :cve_nist:`2025-1125`
|
||||
* - ``gstreamer1.0``
|
||||
- :cve_nist:`2024-47606`
|
||||
* - ``gstreamer1.0-plugins-base``
|
||||
- :cve_nist:`2024-47538`, :cve_nist:`2024-47541`, :cve_nist:`2024-47542`, :cve_nist:`2024-47600`, :cve_nist:`2024-47607`, :cve_nist:`2024-47615`, :cve_nist:`2024-47835`
|
||||
* - ``gstreamer1.0-plugins-good``
|
||||
- :cve_nist:`2024-47537`, :cve_nist:`2024-47539`, :cve_nist:`2024-47540`, :cve_nist:`2024-47543`, :cve_nist:`2024-47544`, :cve_nist:`2024-47545`, :cve_nist:`2024-47546`, :cve_nist:`2024-47596`, :cve_nist:`2024-47597`, :cve_nist:`2024-47598`, :cve_nist:`2024-47599`, :cve_nist:`2024-47601`, :cve_nist:`2024-47602`, :cve_nist:`2024-47603`, :cve_nist:`2024-47606`, :cve_nist:`2024-47613`, :cve_nist:`2024-47774`, :cve_nist:`2024-47775`, :cve_nist:`2024-47776`, :cve_nist:`2024-47777`, :cve_nist:`2024-47778`, :cve_nist:`2024-47834`
|
||||
* - ``libarchive``
|
||||
- :cve_nist:`2024-57970`, :cve_nist:`2025-25724`, :cve_nist:`2025-1632`
|
||||
- :cve_nist:`2024-57970`, :cve_nist:`2025-1632`, :cve_nist:`2025-25724`
|
||||
* - ``libcap``
|
||||
- :cve_nist:`2025-1390`
|
||||
* - ``libsndfile1``
|
||||
- :cve_nist:`2024-50612`
|
||||
* - ``libssh2``
|
||||
- :cve_nist:`2023-48795`
|
||||
* - ``libtasn1``
|
||||
- :cve_nist:`2024-12133`
|
||||
* - ``libxml2``
|
||||
- :cve_nist:`2025-24928`, :cve_nist:`2024-56171`
|
||||
- :cve_nist:`2024-56171`, :cve_nist:`2025-24928`
|
||||
* - ``ofono``
|
||||
- :cve_nist:`2024-7539`, :cve_nist:`2024-7540`, :cve_nist:`2024-7541`, :cve_nist:`2024-7542`
|
||||
* - ``omvf``
|
||||
- :cve_nist:`2023-45236`, :cve_nist:`2023-45237`, :cve_nist:`2024-25742`
|
||||
* - ``openssh``
|
||||
- :cve_nist:`2025-26465`, :cve_nist:`2025-26466`
|
||||
* - ``openssl``
|
||||
- :cve_nist:`2024-9143`, :cve_nist:`2024-12797`, :cve_nist:`2024-13176`
|
||||
* - ``orc``
|
||||
|
|
@ -847,10 +855,12 @@ The following CVEs have been fixed:
|
|||
- :cve_nist:`2024-41123`, :cve_nist:`2024-41946`
|
||||
* - ``rust``
|
||||
- :cve_nist:`2024-43402`
|
||||
* - ``socat``
|
||||
- :cve_nist:`2024-54661`
|
||||
* - ``tiff``
|
||||
- :cve_nist:`2023-52356`, :cve_nist:`2023-6228`, :cve_nist:`2023-6277`
|
||||
- :cve_nist:`2023-6277`, :cve_nist:`2023-6228`, :cve_nist:`2023-52356`
|
||||
* - ``vim``
|
||||
- :cve_nist:`2024-45306`, :cve_nist:`2024-47814`, :cve_nist:`2025-22134`, :cve_nist:`2025-24014`, :cve_nist:`2025-26603`, :cve_nist:`2025-1215`, :cve_nist:`2025-27423`, :cve_nist:`2025-29768`
|
||||
- :cve_nist:`2024-45306`, :cve_nist:`2024-47814`, :cve_nist:`2025-1215`, :cve_nist:`2025-22134`, :cve_nist:`2025-24014`, :cve_nist:`2025-26603`, :cve_nist:`2025-27423`, :cve_nist:`2025-29768`
|
||||
* - ``webkitgtk``
|
||||
- :cve_nist:`2025-24143`, :cve_nist:`2025-24150`, :cve_nist:`2025-24158`, :cve_nist:`2025-24162`
|
||||
* - ``wpa-supplicant``
|
||||
|
|
@ -1158,32 +1168,32 @@ Recipe Upgrades in |yocto-ver|
|
|||
* - ``gst-devtools``
|
||||
- 1.24.10
|
||||
- 1.24.12
|
||||
* - ``gstreamer1``
|
||||
- .0 1.24.10
|
||||
* - ``gstreamer1.0``
|
||||
- 1.24.10
|
||||
- 1.24.12
|
||||
* - ``gstreamer1``
|
||||
- .0-libav 1.24.10
|
||||
* - ``gstreamer1.0-libav``
|
||||
- 1.24.10
|
||||
- 1.24.12
|
||||
* - ``gstreamer1``
|
||||
- .0-plugins-bad 1.24.10
|
||||
* - ``gstreamer1.0-plugins-bad``
|
||||
- 1.24.10
|
||||
- 1.24.12
|
||||
* - ``gstreamer1``
|
||||
- .0-plugins-base 1.24.10
|
||||
* - ``gstreamer1.0-plugins-base``
|
||||
- 1.24.10
|
||||
- 1.24.12
|
||||
* - ``gstreamer1``
|
||||
- .0-plugins-good 1.24.10
|
||||
* - ``gstreamer1.0-plugins-good``
|
||||
- 1.24.10
|
||||
- 1.24.12
|
||||
* - ``gstreamer1``
|
||||
- .0-plugins-ugly 1.24.10
|
||||
* - ``gstreamer1.0-plugins-ugly``
|
||||
- 1.24.10
|
||||
- 1.24.12
|
||||
* - ``gstreamer1``
|
||||
- .0-python 1.24.10
|
||||
* - ``gstreamer1.0-python``
|
||||
- 1.24.10
|
||||
- 1.24.12
|
||||
* - ``gstreamer1``
|
||||
- .0-rtsp-server 1.24.10
|
||||
* - ``gstreamer1.0-rtsp-server``
|
||||
- 1.24.10
|
||||
- 1.24.12
|
||||
* - ``gstreamer1``
|
||||
- .0-vaapi 1.24.10
|
||||
* - ``gstreamer1.0-vaapi``
|
||||
- 1.24.10
|
||||
- 1.24.12
|
||||
* - ``gtk4``
|
||||
- 4.14.5
|
||||
|
|
|
|||
|
|
@ -2204,7 +2204,7 @@ require root privileges, the fact that some earlier steps ran in a fake
|
|||
root environment does not cause problems.
|
||||
|
||||
The capability to run tasks in a fake root environment is known as
|
||||
"`fakeroot <http://man.he.net/man1/fakeroot>`__", which is derived from
|
||||
":manpage:`fakeroot <fakeroot(1)>`", which is derived from
|
||||
the BitBake keyword/variable flag that requests a fake root environment
|
||||
for a task.
|
||||
|
||||
|
|
|
|||
|
|
@ -400,7 +400,7 @@ Yocto Project:
|
|||
Autobuilder :doc:`here </test-manual/understand-autobuilder>`.
|
||||
|
||||
- *Pseudo:* Pseudo is the Yocto Project implementation of
|
||||
`fakeroot <http://man.he.net/man1/fakeroot>`__, which is used to run
|
||||
:manpage:`fakeroot <fakeroot(1)>`, which is used to run
|
||||
commands in an environment that seemingly has root privileges.
|
||||
|
||||
During a build, it can be necessary to perform operations that
|
||||
|
|
|
|||
|
|
@ -2,13 +2,22 @@
|
|||
# Macros used in the documentation
|
||||
#
|
||||
|
||||
# The DISTRO variable represents the current docs version. It should be used
|
||||
# when referring to the current docs version. See also DISTRO_LATEST_TAG.
|
||||
DISTRO : "5.1"
|
||||
# The DISTRO_LATEST_TAG represents the latest tag on the current branch. It
|
||||
# should be used in HTTP link referring to the current docs version. In these
|
||||
# cases, the DISTRO may point to A.B.999 which does not exist (just used to
|
||||
# represent the latest HEAD revision on the branch). DISTRO_LATEST_TAG should
|
||||
# always point to an existing tag.
|
||||
DISTRO_LATEST_TAG : "5.1"
|
||||
DISTRO_NAME_NO_CAP : "styhead"
|
||||
DISTRO_NAME : "Styhead"
|
||||
DISTRO_NAME_NO_CAP_MINUS_ONE : "scarthgap"
|
||||
DISTRO_NAME_NO_CAP_LTS : "scarthgap"
|
||||
YOCTO_DOC_VERSION : "5.1"
|
||||
DISTRO_REL_TAG : "yocto-5.1"
|
||||
DISTRO_REL_TAG : "yocto-$DISTRO;"
|
||||
DISTRO_REL_LATEST_TAG : "yocto-&DISTRO_LATEST_TAG;"
|
||||
DOCCONF_VERSION : "dev"
|
||||
BITBAKE_SERIES : ""
|
||||
YOCTO_DL_URL : "https://downloads.yoctoproject.org"
|
||||
|
|
|
|||
|
|
@ -2712,13 +2712,12 @@ section in the Yocto Project Development Tasks Manual.
|
|||
``ptest-python-pytest``
|
||||
=======================
|
||||
|
||||
The :ref:`ref-classes-ptest-python-pytest` class can be used in Python-based
|
||||
The :ref:`ref-classes-ptest-python-pytest` class can be inherited in Python-based
|
||||
recipes to automatically configure the :ref:`ref-classes-ptest` class for Python
|
||||
packages leveraging the `pytest <https://docs.pytest.org>`__ unit test framework.
|
||||
|
||||
Within the recipe, the :term:`PTEST_PYTEST_DIR` variable can be overridden to
|
||||
specify the path to the directory containing the tests (default value:
|
||||
``tests``). Test contained in this directory are installed in :term:`D` by the
|
||||
Within the recipe, the :term:`PTEST_PYTEST_DIR` variable specifies the path to
|
||||
the directory containing the tests that will be installed in :term:`D` by the
|
||||
:ref:`ref-tasks-install_ptest_base` task, as well as a specific ``run-ptest``
|
||||
script for this task.
|
||||
|
||||
|
|
|
|||
|
|
@ -393,7 +393,7 @@ If you would prefer not to use the ``install-buildtools`` script, you can instea
|
|||
download and run a pre-built :term:`buildtools` installer yourself with the following
|
||||
steps:
|
||||
|
||||
#. Go to :yocto_dl:`/releases/yocto/yocto-&DISTRO;/buildtools/`, locate and
|
||||
#. Go to :yocto_dl:`/releases/yocto/&DISTRO_REL_LATEST_TAG;/buildtools/`, locate and
|
||||
download the ``.sh`` file corresponding to your host architecture
|
||||
and to :term:`buildtools`, :term:`buildtools-extended` or :term:`buildtools-make`.
|
||||
|
||||
|
|
|
|||
|
|
@ -452,7 +452,7 @@ universal, the list includes them just in case:
|
|||
the Source Directory, if you do, the top-level directory name of the
|
||||
Source Directory is derived from the Yocto Project release tarball.
|
||||
For example, downloading and unpacking poky tarballs from
|
||||
:yocto_dl:`/releases/yocto/&DISTRO_REL_TAG;/`
|
||||
:yocto_dl:`/releases/yocto/&DISTRO_REL_LATEST_TAG;/`
|
||||
results in a Source Directory whose root folder is named poky.
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -143,7 +143,7 @@ system and gives an overview of their function and contents.
|
|||
information on how this variable is used.
|
||||
|
||||
:term:`AR`
|
||||
The minimal command and arguments used to run ``ar``.
|
||||
The minimal command and arguments used to run :manpage:`ar <ar(1)>`.
|
||||
|
||||
:term:`ARCHIVER_MODE`
|
||||
When used with the :ref:`ref-classes-archiver` class,
|
||||
|
|
@ -165,7 +165,8 @@ system and gives an overview of their function and contents.
|
|||
``meta/classes/archiver.bbclass`` file in the :term:`Source Directory`.
|
||||
|
||||
:term:`AS`
|
||||
Minimal command and arguments needed to run the assembler.
|
||||
Minimal command and arguments needed to run the :manpage:`assembler
|
||||
<as(1)>`.
|
||||
|
||||
:term:`ASSUME_PROVIDED`
|
||||
Lists recipe names (:term:`PN` values) BitBake does not
|
||||
|
|
@ -994,55 +995,165 @@ system and gives an overview of their function and contents.
|
|||
variable is a useful pointer in case a bug in the software being
|
||||
built needs to be manually reported.
|
||||
|
||||
:term:`BUILD_AR`
|
||||
Specifies the architecture-specific :manpage:`archiver <ar(1)>` for the
|
||||
build host, and its default definition is derived in part from
|
||||
:term:`BUILD_PREFIX`::
|
||||
|
||||
BUILD_AR = "${BUILD_PREFIX}ar"
|
||||
|
||||
When building a :ref:`ref-classes-native` recipe, :term:`AR` is set to the
|
||||
value of this variable by default.
|
||||
|
||||
The :term:`BUILD_AR` variable should not be set manually, and is rarely
|
||||
used in recipes as :term:`AR` contains the appropriate value depending on
|
||||
the context (native or target recipes). Exception be made for target
|
||||
recipes that need to use the :manpage:`archiver <ar(1)>` from the build
|
||||
host at some point during the build.
|
||||
|
||||
:term:`BUILD_ARCH`
|
||||
Specifies the architecture of the build host (e.g. ``i686``). The
|
||||
OpenEmbedded build system sets the value of :term:`BUILD_ARCH` from the
|
||||
machine name reported by the ``uname`` command.
|
||||
|
||||
:term:`BUILD_AS`
|
||||
Specifies the architecture-specific :manpage:`assembler <as(1)>` for the
|
||||
build host, and its default definition is derived in part from
|
||||
:term:`BUILD_PREFIX`::
|
||||
|
||||
BUILD_AS = "${BUILD_PREFIX}as ${BUILD_AS_ARCH}"
|
||||
|
||||
When building a :ref:`ref-classes-native` recipe, :term:`AS` is set to the
|
||||
value of this variable by default.
|
||||
|
||||
The :term:`BUILD_AS` variable should not be set manually, and is rarely
|
||||
used in recipes as :term:`AS` contains the appropriate value depending on
|
||||
the context (native or target recipes). Exception be made for target
|
||||
recipes that need to use the :manpage:`assembler <as(1)>` from the build
|
||||
host at some point during the build.
|
||||
|
||||
:term:`BUILD_AS_ARCH`
|
||||
Specifies the architecture-specific assembler flags for the build
|
||||
host. By default, the value of :term:`BUILD_AS_ARCH` is empty.
|
||||
|
||||
:term:`BUILD_CC`
|
||||
Specifies the architecture-specific C compiler for the build host,
|
||||
and its default definition is derived in part from :term:`BUILD_PREFIX`
|
||||
and :term:`BUILD_CC_ARCH`::
|
||||
|
||||
BUILD_CC = "${CCACHE}${BUILD_PREFIX}gcc ${BUILD_CC_ARCH}"
|
||||
|
||||
When building a :ref:`ref-classes-native` recipe, :term:`CC` is set to the
|
||||
value of this variable by default.
|
||||
|
||||
The :term:`BUILD_CC` variable should not be set manually, and is rarely
|
||||
used in recipes as :term:`CC` contains the appropriate value depending on
|
||||
the context (native or target recipes). Exception be made for target
|
||||
recipes that need to use the compiler from the build host at some point
|
||||
during the build.
|
||||
|
||||
:term:`BUILD_CC_ARCH`
|
||||
Specifies the architecture-specific C compiler flags for the build
|
||||
host. By default, the value of :term:`BUILD_CC_ARCH` is empty.
|
||||
|
||||
:term:`BUILD_CCLD`
|
||||
Specifies the linker command to be used for the build host when the C
|
||||
compiler is being used as the linker. By default, :term:`BUILD_CCLD`
|
||||
points to GCC and passes as arguments the value of
|
||||
:term:`BUILD_CC_ARCH`, assuming
|
||||
:term:`BUILD_CC_ARCH` is set.
|
||||
Specifies the :manpage:`linker <ld(1)>` command to be used for the build
|
||||
host when the C compiler is being used as the linker, and its default
|
||||
definition is derived in part from :term:`BUILD_PREFIX` and
|
||||
:term:`BUILD_CC_ARCH`::
|
||||
|
||||
BUILD_CCLD = "${BUILD_PREFIX}gcc ${BUILD_CC_ARCH}"
|
||||
|
||||
When building a :ref:`ref-classes-native` recipe, :term:`CCLD` is set to
|
||||
the value of this variable by default.
|
||||
|
||||
The :term:`BUILD_CCLD` variable should not be set manually, and is rarely
|
||||
used in recipes as :term:`CCLD` contains the appropriate value depending on
|
||||
the context (native or target recipes). Exception be made for target
|
||||
recipes that need to use the :manpage:`linker <ld(1)>` from the build host
|
||||
at some point during the build.
|
||||
|
||||
:term:`BUILD_CFLAGS`
|
||||
Specifies the flags to pass to the C compiler when building for the
|
||||
build host. When building in the ``-native`` context,
|
||||
build host. When building a :ref:`ref-classes-native` recipe,
|
||||
:term:`CFLAGS` is set to the value of this variable by
|
||||
default.
|
||||
|
||||
:term:`BUILD_CPP`
|
||||
Specifies the C preprocessor command (to both the C and the C++ compilers)
|
||||
when building for the build host, and its default definition is derived in
|
||||
part from :term:`BUILD_PREFIX` and :term:`BUILD_CC_ARCH`::
|
||||
|
||||
BUILD_CPP = "${BUILD_PREFIX}gcc ${BUILD_CC_ARCH} -E"
|
||||
|
||||
When building a :ref:`ref-classes-native` recipe, :term:`CPP` is set to
|
||||
the value of this variable by default.
|
||||
|
||||
The :term:`BUILD_CPP` variable should not be set manually, and is rarely
|
||||
used in recipes as :term:`CPP` contains the appropriate value depending on
|
||||
the context (native or target recipes). Exception be made for target
|
||||
recipes that need to use the preprocessor from the build host at some
|
||||
point during the build.
|
||||
|
||||
:term:`BUILD_CPPFLAGS`
|
||||
Specifies the flags to pass to the C preprocessor (i.e. to both the C
|
||||
and the C++ compilers) when building for the build host. When
|
||||
building in the ``-native`` context, :term:`CPPFLAGS`
|
||||
is set to the value of this variable by default.
|
||||
|
||||
:term:`BUILD_CXX`
|
||||
Specifies the architecture-specific C++ compiler for the build host,
|
||||
and its default definition is derived in part from :term:`BUILD_PREFIX`
|
||||
and :term:`BUILD_CC_ARCH`::
|
||||
|
||||
BUILD_CXX = "${CCACHE}${BUILD_PREFIX}g++ ${BUILD_CC_ARCH}"
|
||||
|
||||
When building a :ref:`ref-classes-native` recipe, :term:`CXX` is set to
|
||||
the value of this variable by default.
|
||||
|
||||
The :term:`BUILD_CXX` variable should not be set manually, and is rarely
|
||||
used in recipes as :term:`CXX` contains the appropriate value depending on
|
||||
the context (native or target recipes). Exception be made for target
|
||||
recipes that need to use the C++ compiler from the build host at some
|
||||
point during the build.
|
||||
|
||||
:term:`BUILD_CXXFLAGS`
|
||||
Specifies the flags to pass to the C++ compiler when building for the
|
||||
build host. When building in the ``-native`` context,
|
||||
build host. When building a :ref:`ref-classes-native` recipe,
|
||||
:term:`CXXFLAGS` is set to the value of this variable
|
||||
by default.
|
||||
|
||||
:term:`BUILD_FC`
|
||||
Specifies the Fortran compiler command for the build host. By
|
||||
default, :term:`BUILD_FC` points to Gfortran and passes as arguments the
|
||||
value of :term:`BUILD_CC_ARCH`, assuming
|
||||
:term:`BUILD_CC_ARCH` is set.
|
||||
Specifies the Fortran compiler command for the build host, and its default
|
||||
definition is derived in part from :term:`BUILD_PREFIX` and
|
||||
:term:`BUILD_CC_ARCH`::
|
||||
|
||||
BUILD_FC = "${BUILD_PREFIX}gfortran ${BUILD_CC_ARCH}"
|
||||
|
||||
When building a :ref:`ref-classes-native` recipe, :term:`FC` is set to the
|
||||
value of this variable by default.
|
||||
|
||||
The :term:`BUILD_FC` variable should not be set manually, and is rarely
|
||||
used in recipes as :term:`FC` contains the appropriate value depending on
|
||||
the context (native or target recipes). Exception be made for target
|
||||
recipes that need to use the Fortran compiler from the build host at some
|
||||
point during the build.
|
||||
|
||||
:term:`BUILD_LD`
|
||||
Specifies the linker command for the build host. By default,
|
||||
:term:`BUILD_LD` points to the GNU linker (ld) and passes as arguments
|
||||
the value of :term:`BUILD_LD_ARCH`, assuming
|
||||
:term:`BUILD_LD_ARCH` is set.
|
||||
Specifies the linker command for the build host, and its default
|
||||
definition is derived in part from :term:`BUILD_PREFIX` and
|
||||
:term:`BUILD_LD_ARCH`::
|
||||
|
||||
BUILD_LD = "${BUILD_PREFIX}ld ${BUILD_LD_ARCH}"
|
||||
|
||||
When building a :ref:`ref-classes-native` recipe, :term:`LD` is set to the
|
||||
value of this variable by default.
|
||||
|
||||
The :term:`BUILD_LD` variable should not be set manually, and is rarely
|
||||
used in recipes as :term:`LD` contains the appropriate value depending on
|
||||
the context (native or target recipes). Exception be made for target
|
||||
recipes that need to use the linker from the build host at some point
|
||||
during the build.
|
||||
|
||||
:term:`BUILD_LD_ARCH`
|
||||
Specifies architecture-specific linker flags for the build host. By
|
||||
|
|
@ -1050,10 +1161,58 @@ system and gives an overview of their function and contents.
|
|||
|
||||
:term:`BUILD_LDFLAGS`
|
||||
Specifies the flags to pass to the linker when building for the build
|
||||
host. When building in the ``-native`` context,
|
||||
host. When building a :ref:`ref-classes-native` recipe,
|
||||
:term:`LDFLAGS` is set to the value of this variable
|
||||
by default.
|
||||
|
||||
:term:`BUILD_NM`
|
||||
Specifies the architecture-specific utility to list symbols from object
|
||||
files for the build host, and its default definition is derived in part
|
||||
from :term:`BUILD_PREFIX`::
|
||||
|
||||
BUILD_NM = "${BUILD_PREFIX}nm"
|
||||
|
||||
When building a :ref:`ref-classes-native` recipe, :term:`NM` is set to the
|
||||
value of this variable by default.
|
||||
|
||||
The :term:`BUILD_NM` variable should not be set manually, and is rarely
|
||||
used in recipes as :term:`NM` contains the appropriate value depending on
|
||||
the context (native or target recipes). Exception be made for target
|
||||
recipes that need to use the utility from the build host at some point
|
||||
during the build.
|
||||
|
||||
:term:`BUILD_OBJCOPY`
|
||||
Specifies the architecture-specific utility to copy object files for the
|
||||
build host, and its default definition is derived in part from
|
||||
:term:`BUILD_PREFIX`::
|
||||
|
||||
BUILD_OBJCOPY = "${BUILD_PREFIX}objcopy"
|
||||
|
||||
When building a :ref:`ref-classes-native` recipe, :term:`OBJCOPY` is set
|
||||
to the value of this variable by default.
|
||||
|
||||
The :term:`BUILD_OBJCOPY` variable should not be set manually, and is
|
||||
rarely used in recipes as :term:`OBJCOPY` contains the appropriate value
|
||||
depending on the context (native or target recipes). Exception be made for
|
||||
target recipes that need to use the utility from the build host at some
|
||||
point during the build.
|
||||
|
||||
:term:`BUILD_OBJDUMP`
|
||||
Specifies the architecture-specific utility to display object files
|
||||
information for the build host, and its default definition is derived in
|
||||
part from :term:`BUILD_PREFIX`::
|
||||
|
||||
BUILD_OBJDUMP = "${BUILD_PREFIX}objdump"
|
||||
|
||||
When building a :ref:`ref-classes-native` recipe, :term:`OBJDUMP` is set
|
||||
to the value of this variable by default.
|
||||
|
||||
The :term:`BUILD_OBJDUMP` variable should not be set manually, and is
|
||||
rarely used in recipes as :term:`OBJDUMP` contains the appropriate value
|
||||
depending on the context (native or target recipes). Exception be made for
|
||||
target recipes that need to use the utility from the build host at some
|
||||
point during the build.
|
||||
|
||||
:term:`BUILD_OPTIMIZATION`
|
||||
Specifies the optimization flags passed to the C compiler when
|
||||
building for the build host or the SDK. The flags are passed through
|
||||
|
|
@ -1074,11 +1233,53 @@ system and gives an overview of their function and contents.
|
|||
build system uses the :term:`BUILD_PREFIX` value to set the
|
||||
:term:`TARGET_PREFIX` when building for :ref:`ref-classes-native` recipes.
|
||||
|
||||
:term:`BUILD_RANLIB`
|
||||
Specifies the architecture-specific utility to generate indexes for
|
||||
archives for the build host, and its default definition is derived in part
|
||||
from :term:`BUILD_PREFIX`::
|
||||
|
||||
BUILD_RANLIB = "${BUILD_PREFIX}ranlib -D"
|
||||
|
||||
When building a :ref:`ref-classes-native` recipe, :term:`RANLIB` is set to
|
||||
the value of this variable by default.
|
||||
|
||||
The :term:`BUILD_RANLIB` variable should not be set manually, and is
|
||||
rarely used in recipes as :term:`RANLIB` contains the appropriate value
|
||||
depending on the context (native or target recipes). Exception be made for
|
||||
target recipes that need to use the utility from the build host at some
|
||||
point during the build.
|
||||
|
||||
:term:`BUILD_READELF`
|
||||
Specifies the architecture-specific utility to display information about
|
||||
ELF files for the build host, and its default definition is derived in
|
||||
part from :term:`BUILD_PREFIX`::
|
||||
|
||||
BUILD_READELF = "${BUILD_PREFIX}readelf"
|
||||
|
||||
When building a :ref:`ref-classes-native` recipe, :term:`READELF` is set
|
||||
to the value of this variable by default.
|
||||
|
||||
The :term:`BUILD_READELF` variable should not be set manually, and is
|
||||
rarely used in recipes as :term:`READELF` contains the appropriate value
|
||||
depending on the context (native or target recipes). Exception be made for
|
||||
target recipes that need to use the utility from the build host at some
|
||||
point during the build.
|
||||
|
||||
:term:`BUILD_STRIP`
|
||||
Specifies the command to be used to strip debugging symbols from
|
||||
binaries produced for the build host. By default, :term:`BUILD_STRIP`
|
||||
points to
|
||||
``${``\ :term:`BUILD_PREFIX`\ ``}strip``.
|
||||
Specifies the command to be used to strip debugging symbols from binaries
|
||||
produced for the build host, and its default definition is derived in part
|
||||
from :term:`BUILD_PREFIX`::
|
||||
|
||||
BUILD_STRIP = "${BUILD_PREFIX}strip"
|
||||
|
||||
When building a :ref:`ref-classes-native` recipe, :term:`STRIP` is set to
|
||||
the value of this variable by default.
|
||||
|
||||
The :term:`BUILD_STRIP` variable should not be set manually, and is
|
||||
rarely used in recipes as :term:`STRIP` contains the appropriate value
|
||||
depending on the context (native or target recipes). Exception be made for
|
||||
target recipes that need to use the utility from the build host at some
|
||||
point during the build.
|
||||
|
||||
:term:`BUILD_SYS`
|
||||
Specifies the system, including the architecture and the operating
|
||||
|
|
@ -1283,6 +1484,10 @@ system and gives an overview of their function and contents.
|
|||
:term:`CC`
|
||||
The minimal command and arguments used to run the C compiler.
|
||||
|
||||
:term:`CCLD`
|
||||
The minimal command and arguments used to run the linker when the C
|
||||
compiler is being used as the linker.
|
||||
|
||||
:term:`CFLAGS`
|
||||
Specifies the flags to pass to the C compiler. This variable is
|
||||
exported to an environment variable and thus made visible to the
|
||||
|
|
@ -2838,6 +3043,9 @@ system and gives an overview of their function and contents.
|
|||
:term:`FAKEROOTNOENV`
|
||||
See :term:`bitbake:FAKEROOTNOENV` in the BitBake manual.
|
||||
|
||||
:term:`FC`
|
||||
The minimal command and arguments used to run the Fortran compiler.
|
||||
|
||||
:term:`FEATURE_PACKAGES`
|
||||
Defines one or more packages to include in an image when a specific
|
||||
item is included in :term:`IMAGE_FEATURES`.
|
||||
|
|
@ -3490,6 +3698,20 @@ system and gives an overview of their function and contents.
|
|||
- mips
|
||||
- mipsel
|
||||
|
||||
:term:`HOST_AS_ARCH`
|
||||
Specifies architecture-specific assembler flags.
|
||||
|
||||
Default initialization for :term:`HOST_AS_ARCH` varies depending on what
|
||||
is being built:
|
||||
|
||||
- :term:`TARGET_AS_ARCH` when building for the
|
||||
target
|
||||
|
||||
- :term:`BUILD_AS_ARCH` when building for the build host (i.e.
|
||||
``-native``)
|
||||
|
||||
- :term:`SDK_AS_ARCH` when building for an SDK (i.e. ``nativesdk-``)
|
||||
|
||||
:term:`HOST_CC_ARCH`
|
||||
Specifies architecture-specific compiler flags that are passed to the
|
||||
C compiler.
|
||||
|
|
@ -3503,8 +3725,20 @@ system and gives an overview of their function and contents.
|
|||
- :term:`BUILD_CC_ARCH` when building for the build host (i.e.
|
||||
``-native``)
|
||||
|
||||
- ``BUILDSDK_CC_ARCH`` when building for an SDK (i.e.
|
||||
``nativesdk-``)
|
||||
- :term:`SDK_CC_ARCH` when building for an SDK (i.e. ``nativesdk-``)
|
||||
|
||||
:term:`HOST_LD_ARCH`
|
||||
Specifies architecture-specific linker flags.
|
||||
|
||||
Default initialization for :term:`HOST_LD_ARCH` varies depending on what
|
||||
is being built:
|
||||
|
||||
- :term:`TARGET_LD_ARCH` when building for the target
|
||||
|
||||
- :term:`BUILD_LD_ARCH` when building for the build host (i.e.
|
||||
``-native``)
|
||||
|
||||
- :term:`SDK_LD_ARCH` when building for an SDK (i.e. ``nativesdk-``)
|
||||
|
||||
:term:`HOST_OS`
|
||||
Specifies the name of the target operating system, which is normally
|
||||
|
|
@ -4539,8 +4773,7 @@ system and gives an overview of their function and contents.
|
|||
|
||||
The value in :term:`INITSCRIPT_PARAMS` is passed through to the
|
||||
``update-rc.d`` command. For more information on valid parameters,
|
||||
please see the ``update-rc.d`` manual page at
|
||||
https://manpages.debian.org/buster/init-system-helpers/update-rc.d.8.en.html
|
||||
please see the manual page: :manpage:`update-rc.d <update-rc.d(8)>`.
|
||||
|
||||
:term:`INSANE_SKIP`
|
||||
Specifies the QA checks to skip for a specific package within a
|
||||
|
|
@ -5190,7 +5423,8 @@ system and gives an overview of their function and contents.
|
|||
``LAYERVERSION_mylayer``).
|
||||
|
||||
:term:`LD`
|
||||
The minimal command and arguments used to run the linker.
|
||||
The minimal command and arguments used to run the :manpage:`linker
|
||||
<ld(1)>`.
|
||||
|
||||
:term:`LDFLAGS`
|
||||
Specifies the flags to pass to the linker. This variable is exported
|
||||
|
|
@ -5805,7 +6039,7 @@ system and gives an overview of their function and contents.
|
|||
variable is set.
|
||||
|
||||
:term:`NM`
|
||||
The minimal command and arguments to run ``nm``.
|
||||
The minimal command and arguments to run :manpage:`nm <nm(1)>`.
|
||||
|
||||
:term:`NO_GENERIC_LICENSE`
|
||||
Avoids QA errors when you use a non-common, non-CLOSED license in a
|
||||
|
|
@ -5906,10 +6140,10 @@ system and gives an overview of their function and contents.
|
|||
NVDCVE_API_KEY = "fe753&7a2-1427-347d-23ff-b2e2b7ca5f3"
|
||||
|
||||
:term:`OBJCOPY`
|
||||
The minimal command and arguments to run ``objcopy``.
|
||||
The minimal command and arguments to run :manpage:`objcopy <objcopy(1)>`.
|
||||
|
||||
:term:`OBJDUMP`
|
||||
The minimal command and arguments to run ``objdump``.
|
||||
The minimal command and arguments to run :manpage:`objdump <objdump(1)>`.
|
||||
|
||||
:term:`OE_BINCONFIG_EXTRA_MANGLE`
|
||||
When inheriting the :ref:`ref-classes-binconfig` class,
|
||||
|
|
@ -6817,6 +7051,23 @@ system and gives an overview of their function and contents.
|
|||
The version of the package(s) built by the recipe. By default,
|
||||
:term:`PKGV` is set to :term:`PV`.
|
||||
|
||||
If :term:`PV` contains the ``+`` sign, source control information will be
|
||||
included in :term:`PKGV` later in the packaging phase. For more
|
||||
information, see the :doc:`/dev-manual/external-scm` section of the Yocto
|
||||
Project Development Tasks Manual.
|
||||
|
||||
.. warning::
|
||||
|
||||
Since source control information is included in a late stage by the
|
||||
:ref:`ref-classes-package` class, it cannot be seen from the BitBake
|
||||
environment with ``bitbake -e`` or ``bitbake-getvar``. Instead, after
|
||||
the package is built, the version information can be retrieved with
|
||||
``oe-pkgdata-util package-info <package name>``. See the
|
||||
:ref:`dev-manual/debugging:Viewing Package Information with
|
||||
\`\`oe-pkgdata-util\`\`` section of the Yocto Project Development Tasks
|
||||
Manual for more information on ``oe-pkgdata-util``.
|
||||
|
||||
|
||||
:term:`PN`
|
||||
This variable can have two separate functions depending on the
|
||||
context: a recipe name or a resulting package name.
|
||||
|
|
@ -7159,7 +7410,7 @@ system and gives an overview of their function and contents.
|
|||
:term:`PTEST_PYTEST_DIR`
|
||||
Within the :ref:`ref-classes-ptest-python-pytest` class, the
|
||||
:term:`PTEST_PYTEST_DIR` variable represents the path within the source
|
||||
tree of a Python package holding the unit tests to be tested with the
|
||||
tree of a Python package holding the unit tests to be run with the
|
||||
`pytest <https://docs.pytest.org>`__ framework. The default value for this
|
||||
variable is ``tests``.
|
||||
|
||||
|
|
@ -7230,7 +7481,7 @@ system and gives an overview of their function and contents.
|
|||
QA_EMPTY_DIRS_RECOMMENDATION:/dev = "but all devices must be created at runtime"
|
||||
|
||||
:term:`RANLIB`
|
||||
The minimal command and arguments to run ``ranlib``.
|
||||
The minimal command and arguments to run :manpage:`ranlib <ranlib(1)>`.
|
||||
|
||||
:term:`RCONFLICTS`
|
||||
The list of packages that conflict with packages. Note that packages
|
||||
|
|
@ -7367,6 +7618,9 @@ system and gives an overview of their function and contents.
|
|||
":ref:`bitbake-user-manual/bitbake-user-manual-execution:dependencies`" sections in the
|
||||
BitBake User Manual for additional information on tasks and dependencies.
|
||||
|
||||
:term:`READELF`
|
||||
The minimal command and arguments to run :manpage:`readelf <readelf(1)>`.
|
||||
|
||||
:term:`RECIPE_MAINTAINER`
|
||||
This variable defines the name and e-mail address of the maintainer of a
|
||||
recipe. Such information can be used by human users submitted changes,
|
||||
|
|
@ -7764,11 +8018,21 @@ system and gives an overview of their function and contents.
|
|||
|
||||
Only one archive type can be specified.
|
||||
|
||||
:term:`SDK_AS_ARCH`
|
||||
Specifies architecture-specific assembler flags when building
|
||||
:ref:`ref-classes-nativesdk` recipes. By default, the value of
|
||||
:term:`SDK_AS_ARCH` equals the one of :term:`BUILD_AS_ARCH`.
|
||||
|
||||
:term:`SDK_BUILDINFO_FILE`
|
||||
When using the :ref:`ref-classes-image-buildinfo` class,
|
||||
specifies the file in the SDK to write the build information into. The
|
||||
default value is "``/buildinfo``".
|
||||
|
||||
:term:`SDK_CC_ARCH`
|
||||
Specifies the architecture-specific C compiler flags when building
|
||||
:ref:`ref-classes-nativesdk` recipes. By default, the value of
|
||||
:term:`SDK_CC_ARCH` equals the one of :term:`BUILD_CC_ARCH`.
|
||||
|
||||
:term:`SDK_CUSTOM_TEMPLATECONF`
|
||||
When building the extensible SDK, if :term:`SDK_CUSTOM_TEMPLATECONF` is set to
|
||||
"1" and a ``conf/templateconf.cfg`` file exists in the :term:`Build Directory`
|
||||
|
|
@ -7850,6 +8114,11 @@ system and gives an overview of their function and contents.
|
|||
:term:`SDK_EXT_TYPE` is set to "minimal", and defaults to "1" if
|
||||
:term:`SDK_EXT_TYPE` is set to "full".
|
||||
|
||||
:term:`SDK_LD_ARCH`
|
||||
Specifies architecture-specific linker flags when building
|
||||
:ref:`ref-classes-nativesdk` recipes. By default, the value of
|
||||
:term:`SDK_LD_ARCH` equals the one of :term:`BUILD_LD_ARCH`.
|
||||
|
||||
:term:`SDK_NAME`
|
||||
The base name for SDK output files. The default value (as set in
|
||||
``meta-poky/conf/distro/poky.conf``) is derived from the
|
||||
|
|
@ -8975,8 +9244,8 @@ system and gives an overview of their function and contents.
|
|||
places stamps. The default directory is ``${TMPDIR}/stamps``.
|
||||
|
||||
:term:`STRIP`
|
||||
The minimal command and arguments to run ``strip``, which is used to
|
||||
strip symbols.
|
||||
The minimal command and arguments to run :manpage:`strip <strip(1)>`,
|
||||
which is used to strip symbols.
|
||||
|
||||
:term:`SUMMARY`
|
||||
The short (72 characters or less) summary of the binary package for
|
||||
|
|
|
|||
|
|
@ -29,7 +29,7 @@ and then run the script to hand-install the toolchain.
|
|||
Follow these steps to locate and hand-install the toolchain:
|
||||
|
||||
#. *Go to the Installers Directory:* Go to
|
||||
:yocto_dl:`/releases/yocto/yocto-&DISTRO;/toolchain/`
|
||||
:yocto_dl:`/releases/yocto/&DISTRO_REL_LATEST_TAG;/toolchain/`
|
||||
|
||||
#. *Open the Folder for Your Build Host:* Open the folder that matches
|
||||
your :term:`Build Host` (i.e.
|
||||
|
|
@ -201,7 +201,7 @@ Follow these steps to extract the root filesystem:
|
|||
Image File:* You need to find and download the root filesystem image
|
||||
file that is appropriate for your target system. These files are kept
|
||||
in machine-specific folders in the
|
||||
:yocto_dl:`Index of Releases </releases/yocto/yocto-&DISTRO;/machines/>`
|
||||
:yocto_dl:`Index of Releases </releases/yocto/&DISTRO_REL_LATEST_TAG;/machines/>`
|
||||
in the "machines" directory.
|
||||
|
||||
The machine-specific folders of the "machines" directory contain
|
||||
|
|
@ -245,7 +245,7 @@ Follow these steps to extract the root filesystem:
|
|||
|
||||
Here is an example command that extracts the root filesystem
|
||||
from a previously built root filesystem image that was downloaded
|
||||
from the :yocto_dl:`Index of Releases </releases/yocto/yocto-&DISTRO;/machines/>`.
|
||||
from the :yocto_dl:`Index of Releases </releases/yocto/&DISTRO_REL_LATEST_TAG;/machines/>`.
|
||||
This command extracts the root filesystem into the ``core2-64-sato``
|
||||
directory::
|
||||
|
||||
|
|
|
|||
|
|
@ -87,7 +87,7 @@ Host` by running the ``*.sh`` installation script.
|
|||
You can download a tarball installer, which includes the pre-built
|
||||
toolchain, the ``runqemu`` script, the internal build system,
|
||||
``devtool``, and support files from the appropriate
|
||||
:yocto_dl:`toolchain </releases/yocto/yocto-&DISTRO;/toolchain/>` directory within the Index of
|
||||
:yocto_dl:`toolchain </releases/yocto/&DISTRO_REL_LATEST_TAG;/toolchain/>` directory within the Index of
|
||||
Releases. Toolchains are available for several 32-bit and 64-bit
|
||||
architectures with the ``x86_64`` directories, respectively. The
|
||||
toolchains the Yocto Project provides are based off the
|
||||
|
|
|
|||
|
|
@ -173,7 +173,7 @@ You just need to follow these general steps:
|
|||
root filesystem images.
|
||||
|
||||
If you are going to develop your application on hardware, go to the
|
||||
:yocto_dl:`machines </releases/yocto/yocto-&DISTRO;/machines/>` download area and choose a
|
||||
:yocto_dl:`machines </releases/yocto/&DISTRO_REL_LATEST_TAG;/machines/>` download area and choose a
|
||||
target machine area from which to download the kernel image and root
|
||||
filesystem. This download area could have several files in it that
|
||||
support development using actual hardware. For example, the area
|
||||
|
|
@ -183,7 +183,7 @@ You just need to follow these general steps:
|
|||
|
||||
If you are going to develop your application and then run and test it
|
||||
using the QEMU emulator, go to the
|
||||
:yocto_dl:`machines/qemu </releases/yocto/yocto-&DISTRO;/machines/qemu>` download area. From this
|
||||
:yocto_dl:`machines/qemu </releases/yocto/&DISTRO_REL_LATEST_TAG;/machines/qemu>` download area. From this
|
||||
area, go down into the directory for your target architecture (e.g.
|
||||
``qemux86_64`` for an Intel-based 64-bit architecture). Download the
|
||||
kernel, root filesystem, and any other files you need for your
|
||||
|
|
|
|||
|
|
@ -43,7 +43,7 @@ Host` by running the ``*.sh`` installation script.
|
|||
|
||||
You can download a tarball installer, which includes the pre-built
|
||||
toolchain, the ``runqemu`` script, and support files from the
|
||||
appropriate :yocto_dl:`toolchain </releases/yocto/yocto-&DISTRO;/toolchain/>` directory within
|
||||
appropriate :yocto_dl:`toolchain </releases/yocto/&DISTRO_REL_LATEST_TAG;/toolchain/>` directory within
|
||||
the Index of Releases. Toolchains are available for several 32-bit and
|
||||
64-bit architectures with the ``x86_64`` directories, respectively. The
|
||||
toolchains the Yocto Project provides are based off the
|
||||
|
|
|
|||
|
|
@ -170,17 +170,29 @@ series = [k for k in release_series]
|
|||
previousseries = series[series.index(ourseries)+1:] or [""]
|
||||
lastlts = [k for k in previousseries if k in ltsseries] or "dunfell"
|
||||
|
||||
latestreltag = subprocess.run(["git", "describe", "--abbrev=0", "--tags", "--match", "yocto-*"], capture_output=True, text=True).stdout
|
||||
latestreltag = latestreltag.strip()
|
||||
if latestreltag:
|
||||
if latestreltag.startswith("yocto-"):
|
||||
latesttag = latestreltag[6:]
|
||||
else:
|
||||
# fallback on the calculated version
|
||||
print("Did not find a tag with 'git describe', falling back to %s" % ourversion)
|
||||
latestreltag = "yocto-" + ourversion
|
||||
latesttag = ourversion
|
||||
|
||||
print("Version calculated to be %s" % ourversion)
|
||||
print("Latest release tag found is %s" % latestreltag)
|
||||
print("Release series calculated to be %s" % ourseries)
|
||||
|
||||
replacements = {
|
||||
"DISTRO" : ourversion,
|
||||
"DISTRO_LATEST_TAG": latesttag,
|
||||
"DISTRO_NAME_NO_CAP" : ourseries,
|
||||
"DISTRO_NAME" : ourseries.capitalize(),
|
||||
"DISTRO_NAME_NO_CAP_MINUS_ONE" : previousseries[0],
|
||||
"DISTRO_NAME_NO_CAP_LTS" : lastlts[0],
|
||||
"YOCTO_DOC_VERSION" : ourversion,
|
||||
"DISTRO_REL_TAG" : "yocto-" + ourversion,
|
||||
"DOCCONF_VERSION" : docconfver,
|
||||
"BITBAKE_SERIES" : bitbakeversion,
|
||||
}
|
||||
|
|
@ -318,3 +330,5 @@ with open('releases.rst', 'w') as f:
|
|||
if tag == release_series[series] or tag.startswith('%s.' % release_series[series]):
|
||||
f.write('- :yocto_docs:`%s Documentation </%s>`\n' % (tag, tag))
|
||||
f.write('\n')
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -28,7 +28,7 @@ WKS_FILE ?= "genericarm64.wks.in"
|
|||
EFI_PROVIDER ?= "${@bb.utils.contains("DISTRO_FEATURES", "systemd", "systemd-boot", "grub-efi", d)}"
|
||||
|
||||
# Try to bring up a selection of physical or virtual serial consoles
|
||||
SERIAL_CONSOLES ?= "115200;ttyAMA0 115200;hvc0 115200;ttyS0 115200;ttyS1 115200;ttyS2"
|
||||
SERIAL_CONSOLES ?= "115200;ttyAMA0 115200;hvc0 115200;ttyS0 115200;ttyS1 115200;ttyS2 115200;ttyPS1"
|
||||
|
||||
# Allow u-boot to be built for use with qemu-system-aarch64.
|
||||
# This u-boot is _not_ suitable for use with real hardware, and the expectation
|
||||
|
|
|
|||
|
|
@ -229,6 +229,11 @@ def update_db_file(db_tmp_file, d, database_time):
|
|||
# We haven't managed to download data
|
||||
return False
|
||||
|
||||
# hack for json5 style responses
|
||||
if raw_data[-3:] == ',]}':
|
||||
bb.note("Removing trailing ',' from nvd response")
|
||||
raw_data = raw_data[:-3] + ']}'
|
||||
|
||||
data = json.loads(raw_data)
|
||||
|
||||
index = data["startIndex"]
|
||||
|
|
|
|||
|
|
@ -92,6 +92,7 @@ PACKAGECONFIG ??= " \
|
|||
quotacheck \
|
||||
randomseed \
|
||||
resolved \
|
||||
serial-getty-generator \
|
||||
set-time-epoch \
|
||||
sysusers \
|
||||
timedated \
|
||||
|
|
@ -753,7 +754,7 @@ FILES:${PN} = " ${base_bindir}/* \
|
|||
FILES:${PN}-dev += "${base_libdir}/security/*.la ${datadir}/dbus-1/interfaces/ ${sysconfdir}/rpm/macros.systemd"
|
||||
|
||||
RDEPENDS:${PN} += "kmod dbus util-linux-mount util-linux-umount udev (= ${EXTENDPKGV}) systemd-udev-rules util-linux-agetty util-linux-fsck util-linux-swaponoff util-linux-mkswap"
|
||||
RDEPENDS:${PN} += "${@bb.utils.contains('PACKAGECONFIG', 'serial-getty-generator', '', 'systemd-serialgetty', d)}"
|
||||
RDEPENDS:${PN} += "systemd-serialgetty"
|
||||
RDEPENDS:${PN} += "volatile-binds"
|
||||
|
||||
RRECOMMENDS:${PN} += "${PN}-extra-utils \
|
||||
|
|
|
|||
|
|
@ -0,0 +1,46 @@
|
|||
From e16117fc92688d76a042ad2c590c77d5a987a4ac Mon Sep 17 00:00:00 2001
|
||||
From: Erik Faye-Lund <erik.faye-lund@collabora.com>
|
||||
Date: Fri, 24 Mar 2023 13:31:58 +0100
|
||||
Subject: [PATCH] meson: fix glx-detection without glvnd
|
||||
|
||||
When build without GLVND, Mesa provides GLX as a part of libGL, just
|
||||
like XQuartz does on MacOS. There's nothing really macOS specific about
|
||||
this fallback, so let's drop the condition.
|
||||
|
||||
And just for good measure, let's add in dep_gl as a dependency for
|
||||
the header-check here, in case some one decides to install libGL outside
|
||||
of the default include directory.
|
||||
|
||||
Fixes: 34300551 ("meson: explicitly check for glx dependency")
|
||||
Closes: https://gitlab.freedesktop.org/mesa/demos/-/issues/36
|
||||
Reviewed-by: Hoe Hao Cheng <haochengho12907@gmail.com>
|
||||
|
||||
Upstream-Status: Backport
|
||||
Signed-off-by: Ross Burton <ross.burton@arm.com>
|
||||
---
|
||||
meson.build | 9 +++++----
|
||||
1 file changed, 5 insertions(+), 4 deletions(-)
|
||||
|
||||
diff --git a/meson.build b/meson.build
|
||||
index c1853f94..bc3278e1 100644
|
||||
--- a/meson.build
|
||||
+++ b/meson.build
|
||||
@@ -99,10 +99,11 @@ if not dep_glu.found() and host_machine.system() != 'darwin'
|
||||
endif
|
||||
|
||||
dep_glx = dependency('glx', required: false, disabler : true)
|
||||
-if not dep_glx.found() and host_machine.system() == 'darwin'
|
||||
- # xquartz doesn't have a glx.pc, but it does have the header. And all the
|
||||
- # symbols reside in libGL, so let's just use that.
|
||||
- if cc.check_header('GL/glx.h', dependencies: dep_x11)
|
||||
+if not dep_glx.found()
|
||||
+ # Both Mesa build without GLVND and XQuartz lacks a glx.pc, but does
|
||||
+ # provide the header. And all the symbols reside in libGL, so let's
|
||||
+ # just use that.
|
||||
+ if cc.check_header('GL/glx.h', dependencies: [dep_x11, dep_gl])
|
||||
dep_glx = dep_gl
|
||||
endif
|
||||
endif
|
||||
--
|
||||
2.43.0
|
||||
|
||||
|
|
@ -10,6 +10,7 @@ LIC_FILES_CHKSUM = "file://src/xdemos/glxgears.c;beginline=1;endline=20;md5=9142
|
|||
file://src/xdemos/glxdemo.c;beginline=1;endline=8;md5=b01d5ab1aee94d35b7efaa2ef48e1a06"
|
||||
|
||||
SRC_URI = "https://archive.mesa3d.org/demos/${BPN}-${PV}.tar.xz \
|
||||
file://0001-meson-fix-glx-detection-without-glvnd.patch \
|
||||
"
|
||||
SRC_URI[sha256sum] = "3046a3d26a7b051af7ebdd257a5f23bfeb160cad6ed952329cdff1e9f1ed496b"
|
||||
|
||||
|
|
|
|||
|
|
@ -256,12 +256,6 @@ PACKAGES =+ "libegl-mesa libegl-mesa-dev \
|
|||
"
|
||||
|
||||
do_install:append () {
|
||||
# Drivers never need libtool .la files
|
||||
rm -f ${D}${libdir}/dri/*.la
|
||||
rm -f ${D}${libdir}/egl/*.la
|
||||
rm -f ${D}${libdir}/gallium-pipe/*.la
|
||||
rm -f ${D}${libdir}/gbm/*.la
|
||||
|
||||
# libwayland-egl has been moved to wayland 1.15+
|
||||
rm -f ${D}${libdir}/libwayland-egl*
|
||||
rm -f ${D}${libdir}/pkgconfig/wayland-egl.pc
|
||||
|
|
|
|||
|
|
@ -11,7 +11,7 @@ LIC_FILES_CHKSUM = "\
|
|||
|
||||
DEPENDS += "git-replacement-native"
|
||||
|
||||
SRCREV = "bfca22a52ec54c77ed0d34a56338bc1fe0a3b0db"
|
||||
SRCREV = "c8c1f17867d0cc7d04be225ba4901f2373428be2"
|
||||
PV = "0.3+git"
|
||||
|
||||
inherit native
|
||||
|
|
|
|||
|
|
@ -14,13 +14,13 @@ python () {
|
|||
raise bb.parse.SkipRecipe("Set PREFERRED_PROVIDER_virtual/kernel to linux-yocto-rt to enable it")
|
||||
}
|
||||
|
||||
SRCREV_machine ?= "9f69ed0ac5f665d431fe52bacdda72534172712b"
|
||||
SRCREV_meta ?= "d034c1073cb7f88eaf3ce929ba21ba11503729b2"
|
||||
SRCREV_machine ?= "8569a61bf30561b620c3171431906cd8ddb7d095"
|
||||
SRCREV_meta ?= "d36334a8b9597faf3978548085097c3b54d462d1"
|
||||
|
||||
SRC_URI = "git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine;protocol=https \
|
||||
git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-6.12;destsuffix=${KMETA};protocol=https"
|
||||
|
||||
LINUX_VERSION ?= "6.12.19"
|
||||
LINUX_VERSION ?= "6.12.23"
|
||||
|
||||
LIC_FILES_CHKSUM = "file://COPYING;md5=6bc538ed5bd9a7fc9398086aedcd7e46"
|
||||
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ require recipes-kernel/linux/linux-yocto.inc
|
|||
# CVE exclusions
|
||||
include recipes-kernel/linux/cve-exclusion_6.12.inc
|
||||
|
||||
LINUX_VERSION ?= "6.12.19"
|
||||
LINUX_VERSION ?= "6.12.23"
|
||||
LIC_FILES_CHKSUM = "file://COPYING;md5=6bc538ed5bd9a7fc9398086aedcd7e46"
|
||||
|
||||
DEPENDS += "${@bb.utils.contains('ARCH', 'x86', 'elfutils-native', '', d)}"
|
||||
|
|
@ -17,8 +17,8 @@ DEPENDS += "openssl-native util-linux-native"
|
|||
KMETA = "kernel-meta"
|
||||
KCONF_BSP_AUDIT_LEVEL = "2"
|
||||
|
||||
SRCREV_machine ?= "b2c792d89ac51b1147810021dddab1e9f38ade9c"
|
||||
SRCREV_meta ?= "d034c1073cb7f88eaf3ce929ba21ba11503729b2"
|
||||
SRCREV_machine ?= "c2c450e032c7bf2653e50fc0a87329ce5660b6be"
|
||||
SRCREV_meta ?= "d36334a8b9597faf3978548085097c3b54d462d1"
|
||||
|
||||
PV = "${LINUX_VERSION}+git"
|
||||
|
||||
|
|
|
|||
|
|
@ -18,25 +18,25 @@ KBRANCH:qemux86.104 ?= "v6.12/standard/base"
|
|||
KBRANCH:qemuloongarch64 ?= "v6.12/standard/base"
|
||||
KBRANCH:qemumips64 ?= "v6.12/standard/mti-malta64"
|
||||
|
||||
SRCREV_machine:qemuarm ?= "f7235e5c375b9ba3d49902dd36d4b66eefc19979"
|
||||
SRCREV_machine:qemuarm64 ?= "b2c792d89ac51b1147810021dddab1e9f38ade9c"
|
||||
SRCREV_machine:qemuloongarch64 ?= "b2c792d89ac51b1147810021dddab1e9f38ade9c"
|
||||
SRCREV_machine:qemumips ?= "c102fc13802679cf23f6a41f9ea54294294f7a93"
|
||||
SRCREV_machine:qemuppc ?= "b2c792d89ac51b1147810021dddab1e9f38ade9c"
|
||||
SRCREV_machine:qemuriscv64 ?= "b2c792d89ac51b1147810021dddab1e9f38ade9c"
|
||||
SRCREV_machine:qemuriscv32 ?= "b2c792d89ac51b1147810021dddab1e9f38ade9c"
|
||||
SRCREV_machine:qemux86 ?= "b2c792d89ac51b1147810021dddab1e9f38ade9c"
|
||||
SRCREV_machine:qemux86-64 ?= "b2c792d89ac51b1147810021dddab1e9f38ade9c"
|
||||
SRCREV_machine:qemumips64 ?= "ee2d5ef2e92ca23c5b345ac50bab130c6a9ad0fc"
|
||||
SRCREV_machine ?= "b2c792d89ac51b1147810021dddab1e9f38ade9c"
|
||||
SRCREV_meta ?= "d034c1073cb7f88eaf3ce929ba21ba11503729b2"
|
||||
SRCREV_machine:qemuarm ?= "dfeb3f6f2658b9d6ae4d5abebc184bd498dd59e9"
|
||||
SRCREV_machine:qemuarm64 ?= "c2c450e032c7bf2653e50fc0a87329ce5660b6be"
|
||||
SRCREV_machine:qemuloongarch64 ?= "c2c450e032c7bf2653e50fc0a87329ce5660b6be"
|
||||
SRCREV_machine:qemumips ?= "8c15ba1838fe0cb24f1ced0b24dedad562dbfd7a"
|
||||
SRCREV_machine:qemuppc ?= "c2c450e032c7bf2653e50fc0a87329ce5660b6be"
|
||||
SRCREV_machine:qemuriscv64 ?= "c2c450e032c7bf2653e50fc0a87329ce5660b6be"
|
||||
SRCREV_machine:qemuriscv32 ?= "c2c450e032c7bf2653e50fc0a87329ce5660b6be"
|
||||
SRCREV_machine:qemux86 ?= "c2c450e032c7bf2653e50fc0a87329ce5660b6be"
|
||||
SRCREV_machine:qemux86-64 ?= "c2c450e032c7bf2653e50fc0a87329ce5660b6be"
|
||||
SRCREV_machine:qemumips64 ?= "8a34918e22d2fc3b37282d1929e760747762b74e"
|
||||
SRCREV_machine ?= "c2c450e032c7bf2653e50fc0a87329ce5660b6be"
|
||||
SRCREV_meta ?= "d36334a8b9597faf3978548085097c3b54d462d1"
|
||||
|
||||
# set your preferred provider of linux-yocto to 'linux-yocto-upstream', and you'll
|
||||
# get the <version>/base branch, which is pure upstream -stable, and the same
|
||||
# meta SRCREV as the linux-yocto-standard builds. Select your version using the
|
||||
# normal PREFERRED_VERSION settings.
|
||||
BBCLASSEXTEND = "devupstream:target"
|
||||
SRCREV_machine:class-devupstream ?= "e9cc806c0152fa9993f817cebf42989a3e2530bb"
|
||||
SRCREV_machine:class-devupstream ?= "83b4161a63b87ce40d9f24f09b5b006f63d95b7c"
|
||||
PN:class-devupstream = "linux-yocto-upstream"
|
||||
KBRANCH:class-devupstream = "v6.12/base"
|
||||
|
||||
|
|
@ -44,7 +44,7 @@ SRC_URI = "git://git.yoctoproject.org/linux-yocto.git;name=machine;branch=${KBRA
|
|||
git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-6.12;destsuffix=${KMETA};protocol=https"
|
||||
|
||||
LIC_FILES_CHKSUM = "file://COPYING;md5=6bc538ed5bd9a7fc9398086aedcd7e46"
|
||||
LINUX_VERSION ?= "6.12.19"
|
||||
LINUX_VERSION ?= "6.12.23"
|
||||
|
||||
PV = "${LINUX_VERSION}+git"
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue
Block a user