summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* vulkan-validation-layers: upgrade to 1.3.283.0Tim Orling2024-05-221-3/+3
| | | | | | | | | | | branch=vulkan-sdk-1.3.283 https://github.com/KhronosGroup/Vulkan-ValidationLayers/compare/vulkan-sdk-1.3.280.0...vulkan-sdk-1.3.283 (From OE-Core rev: 6fe89df4cbc0dd23e1b412c93a59d3e2c50d45bb) Signed-off-by: Tim Orling <tim.orling@konsulko.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* spirv-tools: upgrade to 1.3.283.0Tim Orling2024-05-221-2/+2
| | | | | | | | | https://github.com/KhronosGroup/SPIRV-Tools/compare/vulkan-sdk-1.3.280.0...vulkan-sdk-1.3.283 (From OE-Core rev: 7fc9e8bd171a2208f20de9ba31cfa05bc2b29761) Signed-off-by: Tim Orling <tim.orling@konsulko.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* spirv-headers: upgrade to 1.3.283.0Tim Orling2024-05-221-2/+2
| | | | | | | | | https://github.com/KhronosGroup/SPIRV-Headers/compare/vulkan-sdk-1.3.280.0...vulkan-sdk-1.3.283 (From OE-Core rev: 2f76b544f0679d95a1a1f4b8870a82bbd185746e) Signed-off-by: Tim Orling <tim.orling@konsulko.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* vulkan-tools: upgrade to 1.3.283.0Tim Orling2024-05-221-3/+3
| | | | | | | | | | https://github.com/KhronosGroup/Vulkan-Tools/compare/vulkan-sdk-1.3.280.0...vulkan-sdk-1.3.283 [RP: fix branch] (From OE-Core rev: 8e697a8fd9272420d2975b6e923a52fb0584c251) Signed-off-by: Tim Orling <tim.orling@konsulko.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* vulkan-loader: upgrade to 1.3.283.0Tim Orling2024-05-221-3/+3
| | | | | | | | | | https://github.com/KhronosGroup/Vulkan-Loader/compare/vulkan-sdk-1.3.280.0...vulkan-sdk-1.3.283 [RP: fix branch] (From OE-Core rev: c5af929b0f6df24b3dde1ee9159e0ab630727173) Signed-off-by: Tim Orling <tim.orling@konsulko.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* vulkan-headers: upgrade to 1.3.283.0Tim Orling2024-05-221-2/+2
| | | | | | | | | https://github.com/KhronosGroup/Vulkan-Headers/compare/vulkan-sdk-1.3.280.0...vulkan-sdk-1.3.283 (From OE-Core rev: 36bdffee982b94c7f6b437e65ee504dfe7017a74) Signed-off-by: Tim Orling <tim.orling@konsulko.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* glslang: upgrade to 1.3.283.0Tim Orling2024-05-221-2/+2
| | | | | | | | | https://github.com/KhronosGroup/glslang/compare/vulkan-sdk-1.3.280.0...vulkan-sdk-1.3.283.0 (From OE-Core rev: d20f96e6026b7851439a52e25f2837c40ced5863) Signed-off-by: Tim Orling <tim.orling@konsulko.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* toolchain-scripts: export the target endianism and word sizeRoss Burton2024-05-221-0/+9
| | | | | | | | | | | Some build systems (notably, Meson) like to be told when cross-compiling what the target endian and word size is. We don't have these exported via the variables, so add them using siteinfo as a source of data. (From OE-Core rev: c2fee816cae6dbedcb40f15be4a1b9ee91757a64) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meson: don't use deprecated pkgconfig variableRoss Burton2024-05-221-2/+2
| | | | | | | | | | | | As with a previous change to the class[1], the "pkgconfig" entry is now deprecated and "pkg-config" should be used instead. [1] oe-core d64b307891422e290bbe821d4303b3af526bbe17 (From OE-Core rev: 3e441544f1aa7258718a1cadd6836d9cd9dc65ab) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/sdk: remove unused imports from test casesRoss Burton2024-05-225-5/+2
| | | | | | | | | Remove redundant imports. (From OE-Core rev: b6223259458578d8b967aff11d3263dfed496708) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/sdk: rename test casesRoss Burton2024-05-225-7/+7
| | | | | | | | | | | Instead of having a test called eg "assimp", rename it to "cmake" as the point of the test is to verify that CMake works. This should make it clearer what the tests are actually exercising. (From OE-Core rev: ccf7fdc0e5b6df218b319f972cd5ba142c06c243) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* base-files: profile: fix error sh: 1: unknown operandFelix Nilsson2024-05-221-1/+1
| | | | | | | | | Handle errors when SHLVL isn't set. (From OE-Core rev: 5df53fcfe3b70a5312fced3fcc1ba6290f2ee794) Signed-off-by: Felix Nilsson <felixn@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cups: upgrade from 2.4.7 to 2.4.8Chen Qi2024-05-221-1/+1
| | | | | | | (From OE-Core rev: ce1319344cc64b2ffcccba27423e61c93a3c6a36) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* shadow: upgrade from 4.15.0 to 4.15.1Chen Qi2024-05-223-39/+1
| | | | | | | | | | 0001-lib-copydir-copy_entry-use-temporary-stat-buffer.patch is dropped as it has been merged and is in this new release. (From OE-Core rev: 921b010e6e4b3a61779d8c10eb38966560f665f5) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* pciutils: upgrade from 3.11.1 to 3.12.0Chen Qi2024-05-222-6/+9
| | | | | | | | | configure.patch is rebased against the new version. (From OE-Core rev: 88ab0efeda625892f393576fbcc87e9b517103f5) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemd/systemd-boot: upgrade from 255.4 to 255.6Chen Qi2024-05-2229-239/+111
| | | | | | | | | musl patches are refreshed to avoid 'patch-fuzz' error. (From OE-Core rev: 6bc5e3f3cd882c81c972dbd27aacc1ce00e5e59a) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tclibc-newlib: update security cflags overrideAlejandro Hernandez Samaniego2024-05-221-3/+3
| | | | | | | | | | | It appears that it is no longer necessary to disable security cflags for newlib targets, with the exception of RISCV architectures where the linker does not support PIE (From OE-Core rev: 94a3459c77ad48caab42ca816d984fe467042ce3) Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandro@enedino.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* glib-2.0: upgrade 2.80.0 -> 2.80.2Anuj Mittal2024-05-2215-21/+22
| | | | | | | (From OE-Core rev: edd83b608c2e86b3c0e7d2ce864786efeb1d0540) Signed-off-by: Anuj Mittal <anuj.mittal@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* stress-ng: upgrade 0.17.07 -> 0.17.08Anuj Mittal2024-05-221-1/+1
| | | | | | | (From OE-Core rev: 88c553c0d2d646a3bfc6a5ffd3fb32bd66f3d319) Signed-off-by: Anuj Mittal <anuj.mittal@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* harfbuzz: upgrade 8.4.0 -> 8.5.0Anuj Mittal2024-05-221-1/+1
| | | | | | | (From OE-Core rev: 6bebbf2ac30b7f6fb6bb540eaf183ecc81cc86b7) Signed-off-by: Anuj Mittal <anuj.mittal@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rust: correctly link rust-snapshot into build/stage0Alexander Kanavin2024-05-223-42/+2
| | | | | | | | | | | | | | | | | | This does not seem to be used in regular builds, but is beneficial in rust selftest, where it allows dropping a custom patch that is unsuitable for upstream (and was rejected by them). Also remove an obsolete comment that seems related to the code but describes something that was resolved long time ago. I have confirmed that the rust selftest continues to pass with just this one commit on top of master (as the following changes do break the selftest). (From OE-Core rev: bf5732e2b235ce06fa1f24fe8f0dbcbc068500e3) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ncurses: Upgrade 6.4 -> 6.5Peter Marko2024-05-2210-1468/+16
| | | | | | | | | | | | Removed 4 backported patched included in this release. Updated patches by devtool. License-Update: copyright years refreshed (From OE-Core rev: e9962f7033f717591a168e694311523c82c67608) Signed-off-by: Peter Marko <peter.marko@siemens.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ncurses: switch to new mirrorPeter Marko2024-05-222-3/+3
| | | | | | | | | | | | | | | | | github.com/mirror/ncurses is not updated for over a year. Switch to new mirror from Thomas Dickey (ncurses maintainer). Sources are identical. Updated upstream check regex by: * changed dot to underscore as this repo is tagged like this * added v prefix to not propose updates to some old tags * removed third part to not propose updates to development snapshots (From OE-Core rev: ea801be31d051b558fde52f7d6dccf2cd416afb9) Signed-off-by: Peter Marko <peter.marko@siemens.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* openssl: patch CVE-2024-4603Peter Marko2024-05-222-0/+180
| | | | | | | | | Advisory: https://github.com/advisories/GHSA-85xr-ghj6-6m46 (From OE-Core rev: f136006676750ac653cd7804396614210d1e5120) Signed-off-by: Peter Marko <peter.marko@siemens.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: prserv: add bitbake selftestsMichael Opdenacker2024-05-212-0/+388
| | | | | | | | | | | | Run them with "bitbake-selftest prserv.tests" (Bitbake rev: 34287fbf3d6be813aa5b767f540e4662f0d8d18d) Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Cc: Joshua Watt <JPEWhacker@gmail.com> Cc: Tim Orling <ticotimo@gmail.com> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: prserv: import simplificationMichael Opdenacker2024-05-213-65/+6
| | | | | | | | | | | | | | | | | | | | Simplify the importone() hook: - to make it independent from the "history" mode which is client specific. - remove the "history" parameter - we want all values to be imported for binary reproducibility purposes. - using the store_value() function (which warrants you don't save the same value twice and doesn't write when you're using a read-only server) is enough. (Bitbake rev: 000704a53470ab1ead840403b5531f22ebf1fd49) Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Cc: Joshua Watt <JPEWhacker@gmail.com> Cc: Tim Orling <ticotimo@gmail.com> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: prserv: store_value() improvementsMichael Opdenacker2024-05-211-6/+16
| | | | | | | | | | | | | | | | | | | Add a test_checksum_value() to test whether a (version, pkgarch, checksum, value) entry already exists in the database. This is used to protect the store_value() function from an error when trying to store a duplicate entry in the database. Also check whether the current database is open in read-only mode. (Bitbake rev: b7f6c085a7cf8ac83695242a0299e2d5f7abc69a) Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Cc: Joshua Watt <JPEWhacker@gmail.com> Cc: Tim Orling <ticotimo@gmail.com> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: prserv: avoid possible race condition in database codeMichael Opdenacker2024-05-211-14/+11
| | | | | | | | | | | | | | | Remove a possible race condition by allowing a read-only server to create the PR table anyway. This avoids a failure if both a read-only and read-write server try to access an empty database at the same time. (Bitbake rev: b171caec5ebbe579bf4b8b2005930240ae5c8ce2) Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Suggested-by: Joshua Watt <jpewhacker@gmail.com> Cc: Tim Orling <ticotimo@gmail.com> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: prserv: enable database sharingMichael Opdenacker2024-05-212-180/+151
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | sqlite3 can allow multiple processes to access the database simultaneously, but it must be opened correctly. The key change is that the database is no longer opened in "exclusive" mode (defaulting to shared mode). In addition, the journal is set to "WAL" mode, as this is the most efficient for dealing with simultaneous access between different processes. In order to keep the database performance, synchronous mode is set to "off". The WAL journal will protect against incomplete transactions in any given client, however the database will not be protected against unexpected power loss from the OS (which is a fine trade off for performance, and also the same as the previous implementation). The use of a database cursor enabled to remove the _execute() wrapper. The cursor automatically makes sure that the query happens in an atomic transaction and commits when finished. This also removes the need for a "dirty" flag for the database and for explicit database syncing, which simplifies the code. (Bitbake rev: 385833243c495dc68ec26a963136c1ced3f272d0) Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Cc: Tim Orling <ticotimo@gmail.com> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: prserv: add "upstream" server supportMichael Opdenacker2024-05-215-125/+338
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Introduce a PRSERVER_UPSTREAM variable that makes the local PR server connect to an "upstream" one. This makes it possible to implement local fixes to an upstream package (revision "x", in a way that gives the local update priority (revision "x.y"). Update the calculation of the new revisions to support the case when prior revisions are not integers, but have an "x.y..." format." Set the comments in the handle_get_pr() function in serv.py for details about the calculation of the local revision. This is done by going on supporting the "history" mode that wasn't used so far (revisions can return to a previous historical value), in addition to the default "no history" mode (revisions can never decrease). Rather than storing the history mode in the database table itself (i.e. "PRMAIN_hist" and "PRMAIN_nohist"), the history mode is now passed through the client requests. As a consequence, the table name is now "PRMAIN", which is incompatible with what was generated before, but avoids confusion if we kept the "PRMAIN_nohist" name for both "history" and "no history" modes. Update the server version to "2.0.0". (Bitbake rev: 48857ec3e075791bd73d92747c609a0a4fda0e0c) Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Cc: Joshua Watt <JPEWhacker@gmail.com> Cc: Tim Orling <ticotimo@gmail.com> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: prserv: move code from __init__ to bitbake-prservMichael Opdenacker2024-05-212-14/+8
| | | | | | | | | | | | This script was the only user of this code. (Bitbake rev: 19a5595e3f70d61fd6fa414f9fd5b413a02de37b) Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Cc: Joshua Watt <JPEWhacker@gmail.com> Cc: Tim Orling <ticotimo@gmail.com> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: prserv: declare "max_package_pr" client hookMichael Opdenacker2024-05-211-1/+1
| | | | | | | | | | | | Add missing declaration for the max_package_pr client hook (Bitbake rev: 0d4443359ec38ff98b7fbae0b0948d14f74523ce) Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Cc: Joshua Watt <JPEWhacker@gmail.com> Cc: Tim Orling <ticotimo@gmail.com> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: tests.codeparser: add tests for shell expansionsAntonin Godard2024-05-211-0/+40
| | | | | | | | | | | Tests quotes around `` and $() expansions, nested and multiple expansions, and that escaped quotes are treated as characters by the parser. (Bitbake rev: d98130cb4d500c495bc692c56dde3e019f36320a) Signed-off-by: Antonin Godard <antoningodard@pm.me> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: codeparser: remove redundant list conversionAntonin Godard2024-05-211-1/+1
| | | | | | | (Bitbake rev: 89712949de9476e4674864a8dcd6862fefe92eae) Signed-off-by: Antonin Godard <antoningodard@pm.me> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: codeparser: support shell substitutions in quotesAntonin Godard2024-05-211-7/+22
| | | | | | | | | | | | | | | | | | | | | | | | | The current shell substitution mechanism only works without quotes. For example: var1=$(cmd1 ...) Will work and add `cmd1` to the correspondind `run.do_*` file. However, although quite common, this syntax is not supported: var1="$(cmd1 ...)" This commit adds this feature by adding a step to process_words() to check whether we are dealing with quotes first, and by iterating on what's between them to detect new shell substitution candidates. These candidates are tested and parsed like before in the next step. The original `part` being part of the candidates means the syntax var1=$(cmd1 ...) is still valid. (Bitbake rev: f56e1a37b2ba1773ed308043d7eb073cc2e6c06e) Signed-off-by: Antonin Godard <antoningodard@pm.me> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* genericarm64: depend on u-boot in testimageRoss Burton2024-05-211-0/+3
| | | | | | | | | | | | | | | | | | | | | | genericarm64 supports runqemu, so testimage should work. However, out of the box it does not: runqemu - ERROR - BIOS .../tmp/deploy/images/genericarm64/u-boot.bin not found That is because we make the user explicitly build the qemu-targetting u-boot to avoid the confusing situation where they have real hardware but the deploy directory contains a u-boot for qemu. In automated testing situations, however, we can be a bit more helpful and make testimage depend on u-boot. This will lead to u-boot binaries being in deploy, but at this point the user is already running the images inside a qemu. Reported-by: James McGregor <James.McGregor2@arm.com> (From meta-yocto rev: 90b45c62d34396a20078b55d7d36f66b4e2177f7) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tiny-init: Stop using S == WORKDIRRichard Purdie2024-05-211-3/+4
| | | | | | (From meta-yocto rev: 48fbd32e201667de886b9d5c14807d3958152482) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gtk+3: add gtk+ to CVE_PRODUCTEmil Kronborg2024-05-211-1/+1
| | | | | | | | | | | | | | While the plus in GTK+ was dropped in GTK4 and onwards [1], it is still necessary for GTK3. This is also reflected upstream where two versions exist: http://ftp.gnome.org/pub/gnome/sources/gtk+ and http://ftp.gnome.org/pub/gnome/sources/gtk. [1]: https://mail.gnome.org/archives/gtk-devel-list/2019-February/msg00000.html (From OE-Core rev: 378e1f415855feabe88b168e14f8d367f388e4bc) Signed-off-by: Emil Kronborg <emil.kronborg@protonmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* git: set --with-gitconfig=/etc/gitconfig for -native buildsRasmus Villemoes2024-05-211-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Commit 6c2ae2346db0 (kern-tools: depend on git-replacement-native) broke our kernel builds. For saving space and time, we have a DL_DIR shared between multiple users/buildbots, not all of which run with the same uid (and with appropriate sticky bits set so that files downloaded by one user become owned by a common group and are readable by others). This works fine also for git sources because the docker images we use all have a /etc/gitconfig with [safe] directory = * But with the mentioned commit, the host's git is no longer used for do_unpack (nor for do_fetch if re-building and sysroot has already been populated by a previous build), causing spurious "fatal: detected dubious ownership..." failures. Currently, the path where the git-native binary searches for system gitconfig is the sysroot from it was built, which obviously doesn't contain a /etc/gitconfig. As for the nativesdk variant, respect the host's /etc/gitconfig if present. (From OE-Core rev: 572f511f7ff02fb559ac42d2d5dbd09fec478d97) Signed-off-by: Rasmus Villemoes <rasmus.villemoes@prevas.dk> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-runtime: libgomp fix for gcc 14 warnings with mandb selftestRichard Purdie2024-05-211-1/+1
| | | | | | | | | | | ERROR: gcc-runtime-14.1.0-r0 do_package: QA Issue: gcc-runtime: Files/directories were installed but not shipped in any package: /usr/share/info /usr/share/info/libgomp.info-2 /usr/share/info/libgomp.info-1 (From OE-Core rev: 4f73ddd6c276dcd579d2113db1974d446dbf7751) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/sdk/assimp: Upgrade and fix for gcc 14Richard Purdie2024-05-211-4/+4
| | | | | | | | | To enable this test to work with gcc 14, pass the option to make warnings non-fatal. Also upgrade to version 5.4.1 from 5.3.1. (From OE-Core rev: c3df6287ae26dc9d7f11eb7e26fdbcaefe4dfead) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/sdkext/devtool: replace use of librdfaRoss Burton2024-05-211-4/+3
| | | | | | | | | | | librdfa hasn't had a commit for a decade now and as such has problems with modern compilers (specifically gcc 14.1). Switch the recipe creation test to something much simpler that we also control: dbus-wait. (From OE-Core rev: d801de1f702d8d0def55011b5b6ad39d85f978f1) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Upgrade to GCC 14.1 releaseKhem Raj2024-05-2141-3483/+214
| | | | | | | | | | | | | | | | | | This is major release upgrade. major changes are listed in [1] and it has a list of bugs [2] fixed as well This release may differ in significant ways from prior gcc releases where it may require port the code to gcc 14, there is a porting guide [3] available. [1] https://gcc.gnu.org/gcc-14/changes.html [2] https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=14.0 [3] https://gcc.gnu.org/gcc-14/porting_to.html (From OE-Core rev: fc48aa30e91ffe94f1012fe108fb1db5233a0bc0) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemd: fix build against 6.9 libc-headersBruce Ashfield2024-05-212-0/+54
| | | | | | | | | | | | | | | | | | When building against the 6.9 linux-libc-headrs the following build issue was hit: | Program check-filesystems.sh found: YES (build/tmp/work/cortexa57-poky-linux/systemd/255.4/git/src/basic/check-filesystems.sh) | | ../git/src/basic/meson.build:238:8: ERROR: Problem encountered: Unknown filesystems defined in kernel headers: | | Filesystem found in kernel header but not in filesystems-gperf.gperf: PID_FS_MAGIC Upstream already has this fixed, so we backport the commit. (From OE-Core rev: 5a8a116b270d26ce50429aa32f2883a9d2fd1206) Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto: Avoid QA checkRichard Purdie2024-05-211-0/+5
| | | | | | | | | | The kernel has special handling of ${S} and it is therefore expected to be empty at do_unpack time. For now, ignore this QA check until the kernel unpack process can be more standardised. (From OE-Core rev: f2f3f965d6d5fc19b357891e8c55473782124662) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* go: Drop fork of unpack code, mandate GO_SRCURI_DESTSUFFIXRichard Purdie2024-05-212-15/+3
| | | | | | | | | | | | | | | | | The go class has its own fork of the base unpack code. At the time I was told this was fine, it now isn't as that code is changing. Rather than have a fork, put the path magic into a variable and then go recipes can just set SRC_URI appropriately, e.g.: git://go.googlesource.com/example;branch=master;protocol=https;destsuffix=${GO_SRCURI_DESTSUFFIX} This avoids having special case hacks in the class and makes everything a little more obvious. (From OE-Core rev: cc4ec43a2b657fb4c58429ab14f1edc2473c1327) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Remove warning about S not existingRichard Purdie2024-05-211-0/+5
| | | | | | | | | Disable the qe checks the cause a warning about S not existing as this recipe is special case where that doens't matter. (From OE-Core rev: 99db8d07c74e1580242add9fd9b6f77f1b893b27) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* recipes: Ensure S is set to a valid directoryRichard Purdie2024-05-217-2/+20
| | | | | | | | | | | | Several recipes have S pointing at a directory that does not exist. Set S in these cases to somethig valid making the metadata and recipe behaviour more consistent. Tweak one of the QA test diff offsets to match the changed recipe. (From OE-Core rev: 22f1f5849a9a3bf287dbe8933546e52e39ddc86e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemd-conf: Convert to use a dedicated UNPACKDIRRichard Purdie2024-05-211-5/+8
| | | | | | | | | | | | | | | Avoid: WARNING: systemd-conf-1_1.0-r0 do_unpack: systemd-conf: the directory ${WORKDIR}/${BP} (tmp/work/genericarm64-poky-linux/systemd-conf/1.0/systemd-conf-1.0) pointed to by the S variable doesn't exist - please set S within the recipe to point to where the source has been unpacked to by using a dedicated unpack directory for sources. (From OE-Core rev: 7804eb02bccc5f7f9f84f41ce782bfcfd94bfcc7) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* devtool: Drop oe-local-files and simplifyRichard Purdie2024-05-215-222/+89
| | | | | | | | | | | | | | | | | | | | The only real reason for oe-local-files was to support S = WORKDIR. With changes to drop support for that, it makes sense to simplify devtool and to try and make both the code and the processes/workflows simpler. This patch drops support for S = WORKDIR, removes oe-local-files and then updates the test cases to match this new situation. At the code level, we assume we can always now track code changes using git and that things committed into git are handled as patches (as before) but delta against HEAD is saved as specific file level changes to the recipe. One test is disabled as it is no longer approproate. It is being keped until we can make WORKDIR != UNPACKDIR at which point it should be revisited. (From OE-Core rev: ce8190c519052fed10b5233697b69a75868db45a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2025-08-05 12:01:51 +0000