summaryrefslogtreecommitdiffstats
path: root/meta
Commit message (Collapse)AuthorAgeFilesLines
* qemu: remove obsolete support for renamed libtoolRoss Burton2021-12-121-2/+0
| | | | | | | | | | libtool is now longer renamed to ${host}-libtool, so remove the changes to support this. (From OE-Core rev: cba76eb9232df9af6b1b82649f3e0c6b99ce668c) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* apr: remove obsolete support for renamed libtoolRoss Burton2021-12-121-3/+5
| | | | | | | | | | | | | | | libtool is now longer renamed to ${host}-libtool, so remove the changes to support this. This means that apr now installs libtool into the build-1 folder, but as this has never been needed before (as we use the system libtool) we can remove it (it contains build paths so is unreproducible). Also add a RDEPENDS on libtool for the target -dev package. (From OE-Core rev: 07c0c780fb79779827dcd7496fac288c179aa259) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* freetype: remove obsolete support for renamed libtoolRoss Burton2021-12-122-34/+1
| | | | | | | | | | libtool is now longer renamed to ${host}-libtool, so remove the changes to support this. (From OE-Core rev: 000f129323e4fda3fed9d6d0e45f0bc0328a737e) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* db: remove obsolete support for renamed libtoolRoss Burton2021-12-121-3/+1
| | | | | | | | | | libtool is now longer renamed to ${host}-libtool, so remove the changes to support this. (From OE-Core rev: 291654cb31ff3568f278d143510f1e9fac573966) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gtk+3: remove obsolete support for renamed libtoolRoss Burton2021-12-123-51/+0
| | | | | | | | | | libtool is now longer renamed to ${host}-libtool, so remove the changes to support this. (From OE-Core rev: df74f8637b63d3b88a1b5bdbca22503b98d2d54b) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* pkgconfig: remove obsolete support for renamed libtoolRoss Burton2021-12-122-46/+0
| | | | | | | | | | libtool is now longer renamed to ${host}-libtool, so remove the changes to support this. (From OE-Core rev: 5a4088a1dce17886d391db25a667dd4e0dbbc5cb) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* binutils: don't expect libtool to be host-prefixedRoss Burton2021-12-121-171/+0
| | | | | | | | | | | | | We update the libtool m4 files in binutils with the latest files from our patched libtool so that we can use the --with-libtool-sysroot option. Remove the chunks that are specific to the libtool renaming, which now doesn't happen. (From OE-Core rev: 30baaf6c20a2e1619439cf3eb8d9ce7cb877d2fa) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libtool: don't prefix the installed binaryRoss Burton2021-12-124-109/+8
| | | | | | | | | | | | | | | | | | | | | | Typically libtool installs the binary to 'libtool' in the source tree, but we've got patches to rename this to ${host_sys}-libtool. As this isn't standard any upstream that don't respect the LIBTOOL variable need to be told explicitly where libtool is, which is a long-term maintenance burden for us on top of the initial libtool patches. The reasoning for this renaming appears to stem from the design to be sure that we're using our new/patched libtool and not the host's binary. However, now that we have HOSTTOOLS, there's no way to run the host libtool so this argument is moot. This patch removes the libtool renaming, follow-up patches remove the required modifications from the rest of the recipes. [RP: Remove commented patch lines] (From OE-Core rev: 4b308773eca7570ce5007e8f953b56252c17fdb1) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* elf: Discard input .note.gnu.build-id sectionsValerii Chernous2021-12-122-0/+216
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Originally issue: building of glibc 2.32 or 2.34 with option "-Wl,--build-id" produce libc.so.6 with section ".note.gnu.build-id" that have invalid(double, 0x48) section size. It happens because glibc use sublibraries for linking libc.so.6 ld produce this sublibraries with build-id section and on last linking stage loads this sections as input for linking. ld should create new(valid) ".note.gnu.build-id" into function ldelf_setup_build_id on last linking stage but it skip creating because build-id section already exists. As result libc.so.6 contain ".note.gnu.build-id" with build-ids from sublibraries and without valid build-id Howto solved: 1. Discard input .note.gnu.build-id sections. 2. Clear the build ID field before writing. 3. Use bfd_make_section_anyway_with_flags to create the output .note.gnu.build-id section. Upstream-Status: Backport Reference to upstream patch: [https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=1f1d0f8888a6c944e612b416a2a6e11abcf5199f] (From OE-Core rev: 68bbff44a481a036dc7d39e5d5745a01ccffdb95) Signed-off-by: Valerii Chernous <vchernou@cisco.com> Signed-off-by: Valery Chernous <valery.chernous@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* glibc: Redo tzselect bash dependency problemKhem Raj2021-12-125-36/+61
| | | | | | | | | | | New patch adds a knob to select needed shell interpreter for tzselect script, which then we excercise via EXTRA_OEMAKE (From OE-Core rev: 28adfbbcf42d15eabdd7fe3a5dea486bd5049f09) Signed-off-by: Khem Raj <raj.khem@gmail.com> Cc: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libx11: update to 1.7.3Oleksandr Kravchuk2021-12-123-102/+12
| | | | | | | | | Dropped upstreamed patches. (From OE-Core rev: dc3fcb6f9f6b4f54519265a95d59279fceb5cc97) Signed-off-by: Oleksandr Kravchuk <open.source@oleksandr-kravchuk.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstatetests: add a test for moving oe-core around in the filesystemAlexander Kanavin2021-12-121-0/+42
| | | | | | | | | Doing that should not change the task signatures. (From OE-Core rev: a06ceaeaf11aa344e152f3bb6629aa6e000482d3) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3: udpate to 3.10.1Oleksandr Kravchuk2021-12-1224-108/+109
| | | | | | | | | Refreshed patches. (From OE-Core rev: b82ea986a492791716c3da07a7d728edd17654c9) Signed-off-by: Oleksandr Kravchuk <open.source@oleksandr-kravchuk.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* overlayfs: move templates to files directoryVyacheslav Yurkov2021-12-124-42/+49
| | | | | | | (From OE-Core rev: b08ce6d23f2c6c89073ddff90b758360f9ce9fea) Signed-off-by: Vyacheslav Yurkov <uvv.mail@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* overlayfs: update notes on /etcVyacheslav Yurkov2021-12-121-0/+1
| | | | | | | (From OE-Core rev: a883e5188dd47fffb0df6699f0de2d7a26378eba) Signed-off-by: Vyacheslav Yurkov <uvv.mail@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/selftest: unit tests for overlayfs-etcVyacheslav Yurkov2021-12-121-0/+184
| | | | | | | (From OE-Core rev: 3ca1ce7a3779d0b875385eb4045bd5a51dc839da) Signed-off-by: Vyacheslav Yurkov <uvv.mail@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/selftest: overlayfs helper functionVyacheslav Yurkov2021-12-121-16/+16
| | | | | | | | | Move helper functions out of class scope so they can be used in other tests (From OE-Core rev: 439a5a575b8ca27910431c71f01bf310122ff7ab) Signed-off-by: Vyacheslav Yurkov <uvv.mail@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* image: add overlayfs-etc image featureVyacheslav Yurkov2021-12-121-1/+2
| | | | | | | (From OE-Core rev: e105ee47c5f57a22029e611c7ff9c2376bee9ecb) Signed-off-by: Vyacheslav Yurkov <uvv.mail@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* overlayfs-etc: mount etc as overlayfsVyacheslav Yurkov2021-12-121-0/+76
| | | | | | | | | | | | This class provides an image feature that mounts /etc as an overlayfs file system. This is an extension for existing overlayfs class, which doesn't support /etc (From OE-Core rev: 610ea808c8b5edb2826bda1f1c42a811bd4ba758) Signed-off-by: Alfred Schapansky <alfred.schapansky@avantys.de> Signed-off-by: Vyacheslav Yurkov <uvv.mail@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* files: add overlayfs-etc-preinit.sh.inVyacheslav Yurkov2021-12-121-0/+29
| | | | | | | | | A template init script for overlayfs-etc class (From OE-Core rev: c0173002f3f2118f72307b7e60515287a1b56bda) Signed-off-by: Vyacheslav Yurkov <uvv.mail@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* epiphany: Add packageconfig for libsoup2Joshua Watt2021-12-121-1/+4
| | | | | | | | | | | | | | | Adds a PACKAGECONFIG option to use libsoup2 instead of libsoup3. Including libsoup2 and libsoup3 in the same process can cause strange runtime failures, and the latest release of each major version will cause the process to exit if both are detected on startup. The default is changed from libsoup3 back to libsoup2 to follow webkitgtk. (From OE-Core rev: 430ae4f95a2eb36311338c5c8bdba7331958556a) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* webkitgtk: Add packageconfig for libsoup2Joshua Watt2021-12-121-2/+5
| | | | | | | | | | | | | | | | | | | Adds a PACKAGECONFIG option to use libsoup2 instead of libsoup3. Including libsoup2 and libsoup3 in the same process can cause strange runtime failures, and the latest release of each major version will cause the process to exit if both are detected on startup. The default is changed from libsoup3 back to libsoup2. Most GNOME packages are still using libsoup2, and a large number of these pull in webkitgtk either directly or indirectly. If webkitgtk uses libsoup3, this causes all of these packages to fail at startup. It appears that most GNOME packages will have to switch to libsoup3 when they transition to GTK4. (From OE-Core rev: deedca6bee5c90e35a7814b04bc5de03de9f9b1d) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meson: upgrade 0.60.1 -> 0.60.2Alexander Kanavin2021-12-123-1/+1
| | | | | | | (From OE-Core rev: e020b140cc6eb93283533545c3d64e9aed0b2489) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation: Document PACKAGE_SNAP_LIB_SYMLINKSMike Crowe2021-12-121-0/+1
| | | | | | | | | | | | | | | | | PACKAGE_SNAP_LIB_SYMLINKS was added[1] originally to OpenEmbedded in 2008 and then to oe-core in 2011[2] but appears to have evaded documentation throughout that time. Let's add something that at least gives some clue as to what it does. (From OE-Core rev: f3ee68aa06eb9241789015953c57ccaf9ec9911c) Signed-off-by: Mike Crowe <mac@mcrowe.com> Signed-off-by: Phil Blundell <pb@pbcl.net> [1] https://git.openembedded.org/openembedded/commit/?id=cf7114179ead8ddff8f66e84d630811920ac9add [2] https://git.openembedded.org/openembedded-core/commit/?id=600dbb7cb384c2290af38b993a9bea3a4dfc4494 Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* package: Only snap libraries if they would be processed by ldconfig OS-12840Mike Crowe2021-12-121-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | PACKAGE_SNAP_LIB_SYMLINKS renames libraries based on their SONAME so that they can be found directly rather than going via symlinks that would be created by ldconfig. For example, without PACKAGE_SNAP_LIB_SYMLINKS in ${libdir} we have: libharfbuzz.so.0 -> libharfbuzz.so.0.20600.4 libharfbuzz.so.0.20600.4 but with PACKAGE_SNAP_LIB_SYMLINKS="1" we have just: libharfbuzz.so.0 Unfortunately, this renaming is done based on the SONAME which breaks packages like mesa which install a single library with multiple hard links: -rwxr-xr-x root/root 13593488 2021-12-07 12:26 ./usr/lib/dri/i915_dri.so -rwxr-xr-x root/root 13137328 2021-12-07 12:26 ./usr/lib/dri/i965_dri.so hrwxr-xr-x root/root 0 2021-12-07 12:26 ./usr/lib/dri/iris_dri.so link to ./usr/lib/dri/i915_dri.so hrwxr-xr-x root/root 0 2021-12-07 12:26 ./usr/lib/dri/kms_swrast_dri.so link to ./usr/lib/dri/i915_dri.so hrwxr-xr-x root/root 0 2021-12-07 12:26 ./usr/lib/dri/nouveau_vieux_dri.so link to ./usr/lib/dri/i965_dri.so hrwxr-xr-x root/root 0 2021-12-07 12:26 ./usr/lib/dri/r200_dri.so link to ./usr/lib/dri/i965_dri.so hrwxr-xr-x root/root 0 2021-12-07 12:26 ./usr/lib/dri/radeon_dri.so link to ./usr/lib/dri/i965_dri.so hrwxr-xr-x root/root 0 2021-12-07 12:26 ./usr/lib/dri/swrast_dri.so link to ./usr/lib/dri/i915_dri.so The SONAME for i915_dri.so (and therefore all the other names that link to the same file) is libgallium_dri.so. This means that PACKAGE_SNAP_LIB_SYMLINKS causes do_package to successfully rename the first name found to libgallium_dri.so. A similar thing happens to i965_dri.so with its SONAME of libmesa_dri_drivers.so. The order is not deterministic, so this means that although every build will be missing one name, it's not always the same one. -rwxr-xr-x root/root 13593488 2021-11-30 15:17 ./usr/lib/dri/i915_dri.so hrwxr-xr-x root/root 0 2021-11-30 15:17 ./usr/lib/dri/kms_swrast_dri.so link to ./usr/lib/dri/i915_dri.so hrwxr-xr-x root/root 0 2021-11-30 15:17 ./usr/lib/dri/libgallium_dri.so link to ./usr/lib/dri/i915_dri.so -rwxr-xr-x root/root 13137328 2021-11-30 15:17 ./usr/lib/dri/libmesa_dri_drivers.so hrwxr-xr-x root/root 0 2021-11-30 15:17 ./usr/lib/dri/nouveau_vieux_dri.so link to ./usr/lib/dri/libmesa_dri_drivers.so hrwxr-xr-x root/root 0 2021-11-30 15:17 ./usr/lib/dri/r200_dri.so link to ./usr/lib/dri/libmesa_dri_drivers.so hrwxr-xr-x root/root 0 2021-11-30 15:17 ./usr/lib/dri/radeon_dri.so link to ./usr/lib/dri/libmesa_dri_drivers.so hrwxr-xr-x root/root 0 2021-11-30 15:17 ./usr/lib/dri/swrast_dri.so link to ./usr/lib/dri/i915_dri.so This renaming means that the library cannot be found at runtime. The simplest way to avoid this renaming is to only snap libraries that would be processed by ldconfig. (From OE-Core rev: 8571182ece1602ce8e030c98aef17cdc5718a037) Signed-off-by: Mike Crowe <mac@mcrowe.com> Signed-off-by: Phil Blundell <pb@pbcl.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cmake: upgrade 3.22.0 -> 3.22.1Changqing Li2021-12-123-1/+1
| | | | | | | | | | | | This upgrade include a bug fix: Refer: https://gitlab.kitware.com/cmake/cmake/-/issues/22963 https://gitlab.kitware.com/cmake/cmake/-/commit/643fc46bdc13dd57584d5d77eee30a99308ba896 (From OE-Core rev: 63bf94e26443b3790648c393f36203e9954b85de) Signed-off-by: Changqing Li <changqing.li@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libhandy: Backport a makefile header raceMingli Yu2021-12-122-1/+40
| | | | | | | | | | | | | | | | After the commit(8157ecc Separate public and private enums) introduced, there comes a race as below: | In file included from ../git/src/hdy-settings.c:11: | ../git/src/hdy-settings-private.h:16:10: fatal error: hdy-enums-private.h: No such file or directory | 16 | #include "hdy-enums-private.h" So also add private headers like private sources did now to libhandy_sources to fix the issue. (From OE-Core rev: de57b4624e3d2d66268c33c4bf86dcb25abcab32) Signed-off-by: Mingli Yu <mingli.yu@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libpam: Backport ptest fix checking whether files existMingli Yu2021-12-122-0/+66
| | | | | | | | | | | | | | | | | | | | | | | | | | | Backport a patch to check whether files exist. Before the patch: # ./run-xtests.sh . tst-pam_access1 mv: cannot stat '/etc/security/opasswd': No such file or directory PASS: tst-pam_access1 mv: cannot stat '/etc/security/opasswd-pam-xtests': No such file or directory ================== 1 tests passed 0 tests not run ================== After the patch: # ./run-xtests.sh . tst-pam_access1 PASS: tst-pam_access1 ================== 1 tests passed 0 tests not run ================== (From OE-Core rev: 4903fdbace057df2e39c10aaef3440f89748eed2) Signed-off-by: Mingli Yu <mingli.yu@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* binutils: Drop mips XLP support patchRichard Purdie2021-12-122-416/+0
| | | | | | | | | | | | | The kernel has dropped this as of 5.16 and we don't want to carry such patches without active maintainers for such targets. It isn't clear who would even have such hardware and it isn't something we can support. It would be best maintained as a separate layer by those who can test it if needed. (From OE-Core rev: 5cd5075412639c0be9506cf1101737b12894fc5f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* perf: Tweak for mips n64Richard Purdie2021-12-121-1/+3
| | | | | | | | | With the changes to binutils, perf's direct calls to ld break for mips n64. We already have tweaks for n32 so match those with the ones for n64. (From OE-Core rev: 33828620872b80e1c745612e025215666ba755c8) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* binutils: Drop mips default target patchRichard Purdie2021-12-122-58/+0
| | | | | | | | | Similarly to the recent gcc change, we make gcc default to the 64 bit target through configuration now so we don't need to patch this. (From OE-Core rev: 259bcfdac3ad87d269dd18617c784fe14c50b0ad) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* binutils: Add more detail to the ppc patchRichard Purdie2021-12-121-0/+4
| | | | | | | | This adds useful detail from the orginal commit. (From OE-Core rev: 3dea562e9d615384cc5e786eff46ac1f8f41e18e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* binutils: Drop mips gold patchRichard Purdie2021-12-122-48/+0
| | | | | | | | | | | | | | As mentioned in a followup to the patch upstream: https://sourceware.org/legacy-ml/binutils/2016-08/msg00215.html "With 2.16.1, --enable-gold is just ignored when building on mips" so we don't need the patch since 2.16.1. (From OE-Core rev: 3c230c70f28aef21ae986679d783551832b4e3fa) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libva: move PACKAGECONFIG options to libva.incMarkus Volk2021-12-123-5/+9
| | | | | | | | | | | | | | | | | | | This fixes an error in libva-initial build if 'systemd' is in DISTRO_FEATURES and libdrm is set to be built with udev support. | Run-time dependency xfixes found: NO (tried pkgconfig and cmake) | Run-time dependency wayland-client found: YES 1.19.0 | Program wayland-scanner /usr/bin/wayland-scanner found: NO | | ../libva-2.13.0/meson.build:107:4: ERROR: Program 'wayland-scanner /usr/bin/wayland-scanner' not found | | A full log can be found at /home/flk/build/poky/build-rock/tmp/work/cortexa72-cortexa53-crypto-poky-linux/libva-initial/2.13.0-r0/build/meson-logs/meson-log.txt | ERROR: meson failed | WARNING: exit code 1 from a shell command. (From OE-Core rev: cb9923f4e62339192c0d8e3d2852f1e71c1963b9) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Update to master head revision3.5_M1Richard Purdie2021-12-091-2/+2
| | | | | | (From OE-Core rev: 1a6c2a7345199d77ad5aeac8ad337ed80a8aa39b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* uboot-sign: fix the concatenation when multiple U-BOOT configurations are ↵Thomas Perrot2021-12-091-1/+15
| | | | | | | | | | | | | | | | | | specified Some BSPs, especially those of meta-freescale and meta-ti allow to build U-Boot binaries using different configuration for a given target, for example: - UBOOT_CONFIG ??= "tfa-secure-boot tfa" - UBOOT_CONFIG ??= "nand sdcard spi nor" When this is the case the public key wasn't concatenated to all U-Boot binaries built. (From OE-Core rev: dfd71ae3d102f3010c6117d774e9739a322930f6) Signed-off-by: Thomas Perrot <thomas.perrot@bootlin.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kernel: improve transformation from KERNEL_IMAGETYPE_FOR_MAKEMike Crowe2021-12-091-3/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In 526bdd88ccd758204452579333ba188e29270bde the imageType loop in kernel_do_deploy was changed to use KERNEL_IMAGETYPE_FOR_MAKE rather than KERNEL_IMAGETYPES. This broke the special handling for fitImage immediately below because KERNEL_IMAGETYPE_FOR_MAKE never contains fitImage. It has always been my understanding that KERNEL_IMAGETYPE_FOR_MAKE controlled what was passed to make, but KERNEL_IMAGETYPE controlled what was installed/deployed. When the two are different then it's the responsibility of whoever set KERNEL_IMAGETYPE_FOR_MAKE to ensure that whatever comes out of the kernel build system has been transformed in to the requested form by the time of installation. This is what happens for kernel.bbclass's own support for vmlinux.gz. I think this means that for KERNEL_IMAGETYPE vmlinux.gz, kernel.bbclass is responsible for generating vmlinux.gz.initramfs[1] so that kernel_do_deploy can deploy it. This means that the change in 526bdd88ccd758204452579333ba188e29270bde can be reverted, fixing KERNEL_IMAGETYPE = "fitImage". In addition, it ought to be possible for recipes and other classes that use kernel.bbclass to hook into this mechanism by setting KERNEL_IMAGETYPE_FOR_MAKE and performing their own transformations. do_bundle_initramfs calls kernel_do_compile and we don't want it to transform vmlinux to vmlinux.gz at that point, since it will fight against the careful renaming and preserving that do_bundle_initramfs does. Let's separate the transformation out of kernel_do_compile to a new do_transform_kernel task that can be run at the right time. This means that it's also logical to perform the equivalent translation for the kernel with the initramfs in a separate do_transform_bundled_initramfs task too. This leaves two clear customisation points for recipes and other classes to hook into the process and perform their transformations: do_transform_kernel and do_transform_bundled_initramfs. (I care about this because our recipes that use kernel.bbclass also set KERNEL_IMAGETYPE_FOR_MAKE and transform vmlinux into a form suitable for our bootloader after do_compile and do_bundle_initramfs into the format matching KERNEL_IMAGETYPE. I'm unable to successfully bundle an initramfs after 526bdd88ccd758204452579333ba188e29270bde, but I didn't want to just revert that change to reintroduce the bug that it was fixing.) I can't say that I'm entirely happy with this change, but I'm unsure what to do to improve it. I find the way that both the bare kernel and the one with the initramfs both get deployed to be confusing, and a waste of build time. I would like to not actually generate a publishable kernel image at all during do_compile when an initramfs is in use, but I suspect that this would affect valid use cases that I'm not aware of. (From OE-Core rev: 10a4a132e87e835726bf5da81a60f6f509b90765) Signed-off-by: Mike Crowe <mac@mcrowe.com> [1] It could be argued that this should be vmlinux.initramfs.gz, but that would require another special case in kernel_do_deploy and the filename is only visible within this class and the recipes that use it anyway. Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libid3tag: move to meta-oeAlexander Kanavin2021-12-098-219/+0
| | | | | | | | | There are no consumers in oe-core; years ago it used to be gstreamer. (From OE-Core rev: 4bacb37e9fd55d8bf8ead8d6879e95b31e1dfb55) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kern-tools-native: check tags, not commits for new versionsAlexander Kanavin2021-12-091-1/+0
| | | | | | | (From OE-Core rev: da14779d706619261d2f7b7e8ed5fc57a1c5fc03) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* xxhash: upgrade 0.8.0 -> 0.8.1Alexander Kanavin2021-12-092-60/+5
| | | | | | | | License-Update: GPL2 license for cli tool moved to a separate file (From OE-Core rev: 706ed171c0b761a01f01baac92a2f2ad9ba8240b) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libsoup: upgrade 3.0.2 -> 3.0.3Alexander Kanavin2021-12-091-1/+1
| | | | | | | (From OE-Core rev: c1e9f21c3e691664a05d5c0b756c8d65d0c01dd0) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* enchant2: upgrade 2.3.1 -> 2.3.2Alexander Kanavin2021-12-091-1/+1
| | | | | | | (From OE-Core rev: a11b2d47c74740d44b90529da18b1bb5ccbc9f9a) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* diffoscope: upgrade 192 -> 194Alexander Kanavin2021-12-091-1/+1
| | | | | | | (From OE-Core rev: 9cf813fe8c8bd9b3beb89242b19e9782abe3bc48) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* webkitgtk: upgrade 2.34.1 -> 2.34.2Alexander Kanavin2021-12-091-1/+1
| | | | | | | (From OE-Core rev: b5ee08f8f2bafc17ecc39d9c9351cc9b14eb4982) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* piglit: upgrade to latest revisionAlexander Kanavin2021-12-091-1/+1
| | | | | | | (From OE-Core rev: 956ad6a12774e38feaa93bf8a7671a9006160958) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mesa: upgrade 21.3.0 -> 21.3.1Alexander Kanavin2021-12-093-1/+1
| | | | | | | (From OE-Core rev: 1970fd5764adff10a5d7e643aeea7ce40d318f26) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* vulkan-loader: upgrade 1.2.198.0 -> 1.2.198.1Alexander Kanavin2021-12-091-1/+1
| | | | | | | (From OE-Core rev: db741a0a117f21aaa9925b0f930d01eb548a7a07) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* harfbuzz: upgrade 3.1.1 -> 3.1.2Alexander Kanavin2021-12-091-1/+1
| | | | | | | (From OE-Core rev: fd4788c9557e6a88d7e9ffb02d8b75b003507612) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* freetype: upgrade 2.11.0 -> 2.11.1Alexander Kanavin2021-12-091-1/+1
| | | | | | | (From OE-Core rev: 28d330313ceb801727372fd27d1955db5953f96b) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-setuptools: upgrade 59.2.0 -> 59.4.0Alexander Kanavin2021-12-092-2/+2
| | | | | | | (From OE-Core rev: 4c549f4aaf548fcc494ffdb3936b447a545d4624) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2025-01-18 09:58:47 +0000