summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* openssl-native(sdk): poision built in pathsDan McGregor2025-03-062-9/+13
| | | | | | | | | | | | | | | | | | | | Long ago, in the OpenSSL 1.1 days changing CFLAGS worked to override hard-coded paths in the OpenSSL libraries. Even as far back as kirkstone this was no longer working. Override make variables instead to poision the paths that get built into the native (and nativesdk) libraries so they become relocatable again. While here, remove the -isystem<foo> compiler argument from the compiler command line stored in the library, just like we already remove the prefix-map and sysroot arguments. (From OE-Core rev: d1b29222ad6243c15275a04f9de5989cf158cb2e) Signed-off-by: Dan McGregor <dan.mcgregor@usask.ca> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libtasn1: upgrade 4.19.0 -> 4.20.0Vijay Anusuri2025-03-061-4/+3
| | | | | | | | | | | | | | | | | * Noteworthy changes in release 4.20.0 (2025-02-01) [stable] - The release tarball is now reproducible. - We publish a minimal source-only tarball generated by 'git archive'. - Update gnulib files and various build/maintenance fixes. - Fix CVE-2024-12133: Potential DoS in handling of numerous SEQUENCE OF or SET OF elements License-Update: file COPYING.LESSER renamed to COPYING.LESSERv2 & Copyright year updated to 2025 (From OE-Core rev: 3a8633b9f522e0be31c08790a3f2050c6d052d93) Signed-off-by: Vijay Anusuri <vanusuri@mvista.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mirrors: rationalise Debian mirrorsRoss Burton2025-03-062-18/+2
| | | | | | | | | | | | | | | Change DEBIAN_MIRROR to point at the canonical server, deb.debian.org. This is a CDN-backed server using network magic to load balance across the planet so there's no need to set a slew of regional mirrors. Also add a more recent snapshot.debian.org from the beginning of 2025. (From OE-Core rev: 3d95d45836accd29916dd8cb9bfe624d63d6c202) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemd-serialgetty: use existing unit files in systemdRoss Burton2025-03-062-57/+1
| | | | | | | | | | | | | | Now that systemd isn't deleting the serial-getty@.service unit template files, we can simply symlink to the files provided by systemd instead of shipping a copy of them in this recipe. This ensures that the getty units triggered by the systemd are identical, be them via SERIAL_CONSOLES or the generator. (From OE-Core rev: b6a7617145c3acf9f79888e7555e7706cd55a350) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemd: if getty generator is disabled remove the generator, not the unitsRoss Burton2025-03-061-3/+5
| | | | | | | | | | | If the getty generator is disabled then it's neater to remove just the generator tool instead of the unit files as the unit files are still useful. (From OE-Core rev: 2beb3170af6ebf3a6fff6953a2d48f70f61b959f) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemd-serialgetty: don't set a default SERIAL_CONSOLESRoss Burton2025-03-061-1/+0
| | | | | | | | | | bitbake.conf defines a default value, so there's no value in setting another default here that doesn't match the rest of the system. (From OE-Core rev: 86586f4956879ad1b906f198dc258c88f64ef179) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: lib/bb/cooker.py: produce an error when BB_HASHSERVE_UPSTREAM ↵Alexander Kanavin2025-03-061-2/+8
| | | | | | | | | | | | | | | | cannot be used due to missing python module Previously if the websockets module was not installed bitbake would only print a warning and continue, resulting in a degraded user experience due to inability to use the configured sstate server. Let's consider that as fatal misconfiguration, so that users can address the issue properly and not wonder why builds are taking forever. (Bitbake rev: cfba2a9fca9dfa3b05ec9040fe0cb8143ac04af7) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: tests/fetch: Add an additional test case to check whether the fast ↵Stefan Koch2025-03-061-0/+12
| | | | | | | | | fetch is shallow (Bitbake rev: 16f1961e077c525ccfc12496a3deca944df89fc6) Signed-off-by: Stefan Koch <stefan-koch@siemens.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: tests/fetch: Adapt test cases for fast shallow fetchesStefan Koch2025-03-061-19/+12
| | | | | | | | | | | | - Address the absence of an initial full bare clone - Utilize the initial shallow clone - Modify existing test cases for this behavior - Remove incompatible test cases (Bitbake rev: 599fedacd7782dcb52825c22200f35344c102548) Signed-off-by: Stefan Koch <stefan-koch@siemens.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: fetch2/gitsm: Unpack even when `ud.clonedir` is not availableStefan Koch2025-03-061-1/+4
| | | | | | | (Bitbake rev: 13d76361ec37faecd84e7b81da22ada7d4e0ba90) Signed-off-by: Stefan Koch <stefan-koch@siemens.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake-user-manual: Update documentation for fast `BB_GIT_SHALLOW`Stefan Koch2025-03-061-5/+20
| | | | | | | (Bitbake rev: b92c95fab631156e8c7ecc4ab18e4b16f7e590dc) Signed-off-by: Stefan Koch <stefan-koch@siemens.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: fetch2/git: Add support for fast initial shallow fetchStefan Koch2025-03-061-29/+85
| | | | | | | | | | | | | | | | | | | | | | | | When `ud.shallow == 1`: - Prefer an initial shallow clone over an initial full bare clone, while still utilizing any already existing full bare clones. - If the Git error "Server does not allow request for unadvertised object" occurs, the initial full bare clone is fetched automatically. This may happen if the Git server does not allow the request or if the Git client has issues with this functionality, especially with the Git client from Ubuntu 20.04. This improves: - Resolve timeout issues during initial clones on slow internet connections by reducing the amount of data transferred. - Eliminate the need to use an HTTPS tarball `SRC_URI` to reduce data transfer. - Allow SSH-based authentication (e.g. cert and agent-based) when using non-public repos, so additional HTTPS tokens may not be required. (Bitbake rev: 457288b2fda86fd00cdcaefac616129b0029e1f9) Signed-off-by: Stefan Koch <stefan-koch@siemens.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* xserver-nodm-init: improve XDG_RUNTIME_DIR fallback creationRoss Burton2025-03-051-7/+13
| | | | | | | | | | | | | | | | This directory must have mode 0700, and should be under /run/user (as recommended in the specification, and as weston-init does). Also check the permissions if the directory already exists and fail early if they're incorrect. [ YOCTO #13878 ] (From OE-Core rev: 5c98609bf7dfb05af722e30adb49731727df9a94) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* weston-init: improve XDG_RUNTIME_DIR fallback creationRoss Burton2025-03-051-8/+13
| | | | | | | | | | | Sanity-check the permissions of the directory already exists, and clean up the creation code. (From OE-Core rev: a977c2a61dfabed9be061d742797248448aa5ade) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ltp: don't use host objcopyRoss Burton2025-03-052-0/+70
| | | | | | | | | | | | | | | | | The kernel/kvm test uses the host objcopy when building a payload, but the host objcopy might not know how to deal with target binaries: CC testcases/kernel/kvm/lib_host.o objcopy: Unable to recognise the format of the input file `kvm_svm03-payload.elf' make[3]: *** [ltp/testcases/kernel/kvm/Makefile:67: kvm_svm03-payload.o] Error 1 Solve this by using the host-prefixed objcopy binary. (From OE-Core rev: 74818f79bd9a206f77ae3d26b19657116fd956cc) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rust: Oe-selftest changes for rust v1.83.0Deepesh Varatharajan2025-03-051-0/+31
| | | | | | | | | | | | Few unit tests are failing for x86_64 arch. Ignore the failing unit tests. Upstream-Status: Pending (From OE-Core rev: c71f9efc3140d279813ff6eb474fdbf5e677e348) Signed-off-by: Deepesh Varatharajan <Deepesh.Varatharajan@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rust: Fix build break because of download-ci-llvmDeepesh Varatharajan2025-03-051-0/+1
| | | | | | | | | | | | | | | | | | | | Previously, download-ci-llvm was set to false. However, with the following commit: https://github.com/rust-lang/rust/commit/7d579046c80d3de3143dcb8b2db5640f95b5383c , which has been present from rust_1.83, it was changed to true. As a result, after updating to rust_1.83, we encountered the following error during the build: ------------------------------------------------------------------------------- | thread 'main' panicked at src/core/config/config.rs:2047:13: | setting build-target.llvm-config is incompatible with download-ci-llvm. | note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace ------------------------------------------------------------------------------- To resolve this issue, we are setting download-ci-llvm back to false. (From OE-Core rev: d43424cba7e93ee30b410d0a024be441e2336dbd) Signed-off-by: Deepesh Varatharajan <Deepesh.Varatharajan@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rust: Upgrade 1.82.0->1.83.0Deepesh Varatharajan2025-03-0515-243/+249
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Rust stable version updated to 1.83.0. https://blog.rust-lang.org/2024/11/28/Rust-1.83.0.html Renamed and modified the below patch to adapt the new version. rv32-cargo-rustix-0.38.34-fix.patch->rv32-cargo-rustix-0.38.37-fix.patch Modified the below patches to adapt the new version. repro-issue-fix-with-cc-crate-hashmap.patch revert-link-std-statically-in-rustc_driver-feature.patch Dropped: zlib-off64_t.patch https://github.com/madler/zlib/commit/a566e156b3fa07b566ddbf6801b517a9dba04fa3kq Because of the following commit , https://github.com/rust-lang/rust/commit/68034f837a39387e49fc7d7c5b088f5372a1127e when we enable lib32, getting build failure because there is a check for target support for "-Zdual-proc-macros" flag not functioning properly when lib32 is enabled in the build environment. So for now reverting this commit and bring back the previous behavior, where the "-Zdual-proc-macros" flag is always added for building proc macros, regardless of the target architecture's support. This would bypass the check introduced in the patch, allowing the build to proceed without error, even when building for a 64-bit architecture with lib32 enabled. (From OE-Core rev: 40d8dafdf556d7ce79c12a6de872193be9a0928a) Signed-off-by: Deepesh Varatharajan <Deepesh.Varatharajan@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: toaster/tests: Fix kirkstone testRichard Purdie2025-03-051-2/+2
| | | | | | | | After the fixture changes, the tests need to be tweaked unfotunately. (Bitbake rev: 708abd1a8060684127acc7ce4142f05865005750) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: toaster/fixtures: Add walnascar release informationRichard Purdie2025-03-053-28/+90
| | | | | | (Bitbake rev: 44f732ae1b2d812577a9004f8e15c4ebcdfd1d74) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: toaster: Add script to compare toaster fixtures to project release dataRichard Purdie2025-03-051-0/+38
| | | | | | | | | | | | We need to validate the toaster fixtures information against our current release data to ensure it is correct when we release. Add a script we can use to do this which the autobuilder can run to validate things. [YOCTO #15516] (Bitbake rev: 5b2d79ed505bbfa2fb2d355935e75199b7f2c37e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Start to separate out gcc related variable definitionsRichard Purdie2025-03-055-41/+100
| | | | | | | | | | | | To be able to switch toolchains, we need to separate out the gcc definitions into seperate include files. This patch starts that process. Whilst the include is still hardcoded for now, it allows developers to start experimenting with this locally more easily and stops people reinventing this patch. A sample clang configuruation is also included which I was using for experimentation. (From OE-Core rev: be063d58c0985a2c43c16302efb44706fbf3f1b3) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* poky: Remove Fedora38 from SANITY_TESTED_DISTROSRichard Purdie2025-03-051-1/+0
| | | | | | | | | Now the obsolete config is removed from the autobuilder, we should remove this distro from the tested list too. (From meta-yocto rev: 59567ab18a6819ea845c9be824b203d030eb09c4) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* poky: Update SANITY_TESTED_DISTROSRichard Purdie2025-03-051-2/+3
| | | | | | | | | Update the distros list to match what the autobuilder has available as configured and tested workers. (From meta-yocto rev: b3641515b44dcde4ee37e82428699d92b0785f2a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: contrib: vim: ftdetect: don't conflict with other filetypesRoland Hieber2025-03-031-3/+11
| | | | | | | | | | | | | | | | | | | | | | Use :setfiletype instead of :set filetype. The former only sets the 'filetype' option if it has not been set before, which makes it possible to override the syntax of certain *.inc files in autocommands from e.g. .vimrc or modelines. All other ftdetect plugins in upstream vim also use :setfiletype for this reason. The detection for bitbake *.inc files is now upstream since Vim 9.0 patch 0055 [1]. If we're running an earlier Vim, use the detection heuristic from upstream [2] to overwrite the filetype explicitely if we find bitbake code. But don't always assuming that *.inc files are bitbake files so as not to break Perl, PHP, Assembly, Povray, etc. [1]: https://github.com/vim/vim/commit/fa49eb482729 [2]: https://github.com/vim/vim/blob/fb49e3cde79d/runtime/autoload/dist/ft.vim#L715 (Bitbake rev: e8efbba5d7bb4b685ed0a9b970e042ad99be8afb) Signed-off-by: Roland Hieber <rhi@pengutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake: runqueue: Verify mcdepends are validMark Hatle2025-03-034-1/+14
| | | | | | | | | | | | | | | In order to avoid a potentially confusing backtrace, check that the mcdepend is valid when we add it. Add a test case to ensure invalid configurations are caught and trigger an error. [RP: Reworked test case to simplify and improve code] (Bitbake rev: ff523497270f37b484b44a4445c2194791bcb6ff) Signed-off-by: Mark Hatle <mark.hatle@amd.com> Signed-off-by: Mark Hatle <mark.hatle@kernel.crashing.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: event/utils: Avoid deadlock from lock_timeout() and recursive eventsRichard Purdie2025-03-032-1/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We've been seeing intermittent failures on Ubuntu 22.04 in oe-selftest which were problematic to debug. The failure was inside lock_timeout and once that was identified and the backtrace obtained, the problem becomes clearer: File "X/bitbake/lib/bb/server/process.py", line 466, in idle_thread_internal retval = function(self, data, False) File "X/bitbake/lib/bb/command.py", line 123, in runAsyncCommand self.cooker.updateCache() File "X/bitbake/lib/bb/cooker.py", line 1629, in updateCache self.parser = CookerParser(self, mcfilelist, total_masked) File "X/bitbake/lib/bb/cooker.py", line 2141, in __init__ self.bb_caches = bb.cache.MulticonfigCache(self.cfgbuilder, self.cfghash, cooker.caches_array) File "X/bitbake/lib/bb/cache.py", line 772, in __init__ loaded += c.prepare_cache(progress) File "X/bitbake/lib/bb/cache.py", line 435, in prepare_cache loaded = self.load_cachefile(progress) File "X/bitbake/lib/bb/cache.py", line 516, in load_cachefile progress(cachefile.tell() + previous_progress) File "X/bitbake/lib/bb/cache.py", line 751, in progress bb.event.fire(bb.event.CacheLoadProgress(current_progress, cachesize), File "X/bitbake/lib/bb/event.py", line 234, in fire fire_ui_handlers(event, d) File "X/bitbake/lib/bb/event.py", line 210, in fire_ui_handlers _ui_handlers[h].event.send(event) File "X/bitbake/lib/bb/cooker.py", line 117, in send str_event = codecs.encode(pickle.dumps(event), \'base64\').decode(\'utf-8\') File "/usr/lib/python3.10/asyncio/sslproto.py", line 320, in __del__ _warn(f"unclosed transport {self!r}", ResourceWarning, source=self) File "/usr/lib/python3.10/warnings.py", line 109, in _showwarnmsg sw(msg.message, msg.category, msg.filename, msg.lineno, File "X/bitbake/lib/bb/main.py", line 113, in _showwarning warnlog.warning(s) File "/usr/lib/python3.10/logging/__init__.py", line 1489, in warning self._log(WARNING, msg, args, **kwargs) File "/usr/lib/python3.10/logging/__init__.py", line 1624, in _log self.handle(record) File "/usr/lib/python3.10/logging/__init__.py", line 1634, in handle self.callHandlers(record) File "/usr/lib/python3.10/logging/__init__.py", line 1696, in callHandlers hdlr.handle(record) File "/usr/lib/python3.10/logging/__init__.py", line 968, in handle self.emit(record) File "X/bitbake/lib/bb/event.py", line 778, in emit fire(record, None) File "X/bitbake/lib/bb/event.py", line 234, in fire fire_ui_handlers(event, d) File "X/bitbake/lib/bb/event.py", line 197, in fire_ui_handlers with bb.utils.lock_timeout(_thread_lock): File "/usr/lib/python3.10/contextlib.py", line 135, in __enter__ return next(self.gen) File "X/bitbake/lib/bb/utils.py", line 1888, in lock_timeout bb.server.process.serverlog("Couldn\'t get the lock for 5 mins, timed out, exiting. %s" % traceback.format_stack()) or put in simpler terms, whilst sending an event(), an unrelated warning message happens to be triggered from asyncio: /usr/lib/python3.10/asyncio/sslproto.py:320: ResourceWarning: unclosed transport <asyncio.sslproto._SSLProtocolTransport object at 0x7f0e797d3100> which triggers a second event() which can't be sent as we're already in the critcal section and already hold the lock. That warning is due to the version of asyncio used on Ubuntu 22.04 with python 3.10 and that comined with timing issues explains why we don't see it on other python versions or distros. We can't handle the second event as the lock is there to serialise the events. Instead, we queue the event and then process the queue later. Add a new version of lock_timeout which allows us to handle the situation more gracefully. (Bitbake rev: 2c590ff1aff89d23b25ce808650f200013a1e6af) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: utils: Add signal blocking for lock_timeoutRichard Purdie2025-03-031-0/+2
| | | | | | | | | | We never want to exit whilst holding these locks as it deadlocks all python threads. Add signal blocking around the lock critical part so a signal shouldn't cause such an exit. (Bitbake rev: a097755c671e2b530dea6200a94b39fa9dca246c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: utils: Tweak lock_timeout logicRichard Purdie2025-03-031-1/+1
| | | | | | | | | | We should really try and take the lock in the try/finally block so that in some rare cases such as badly timed interrupt/signal, we always release the lock. (Bitbake rev: a9eb8bf7174b6962b5ba07192fe95b8c7112d9d2) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: utils: Print information about lock issue before exitingRichard Purdie2025-03-031-0/+1
| | | | | | (Bitbake rev: cdf6c51a064f8f335c3262b7f102618996f1a229) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemurunner: Fix a bug with fork/exit handlingRichard Purdie2025-03-031-6/+9
| | | | | | | | | | | | | If you send this forked process a SIGTERM, it will execute all of the parent's exit code leading to two sets of console/exit output which is extremely confusing. Wrap the code in a try/finally to ensure we always call os._exit() to avoid this. I spent far too long trying to work out the crazy console output from this. (From OE-Core rev: 652e40bfae24b8e23bbf7a7f35d900d2ab8d0f92) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* maintainers.inc: change email addressMarta Rybczynska2025-03-031-3/+3
| | | | | | | | (From OE-Core rev: 3e09e4d9a19cec68a41faaea555a1ed7b76e576e) Signed-off-by: Marta Rybczynska <marta.rybczynska@ygreky.com> Signed-off-by: Marta Rybczynska <mrybczynska@syslinbit.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3: update python3-ctypes RDEPENDS to RRECOMMENDSChangqing Li2025-03-031-1/+1
| | | | | | | | | | | | | | | | | | | ctypes.util.find_library depend on run external programs(ldconfig, gcc, objdump or ld) to get the pathname, if none of above are installed, None is returned. Previously, RDEPENDS to ldconfig is added to ensure it always work when installed. This commit change it to RRECOMMENDS, this allows user who don't use function find_library could remove ldconfig from image by PACKAGE_EXCLUDE Refer: https://docs.python.org/3/library/ctypes.html (From OE-Core rev: 404e7c65499c58d2a6a760b5f0994fadd2ff74d0) Signed-off-by: Changqing Li <changqing.li@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* go: Check if GO_IMPORT is set in recipe and error if notChristos Gavros2025-03-031-0/+3
| | | | | | | | | | | | | | | | | | | | Check if the variable GO_IMPORT is set in the recipe. If not generate an error. Test building go-helloworld when GO_IMPORT assigned Test building go-helloworld when GO_IMPORT is not assigned, generate error about GO_IMPORT Test building any other recipe(e.g bash) when GO_IMPORT is not assigned, generate error about GO_IMPORT Test creating a GO recipe with recipetool (not affected) Test selftest test_recipetool_create_go (not affected) Test selftest test_recipetool_create_go_replace_modules (not affected) [YOCTO #15763] CC: Yoann Congal <yoann.congal@smile.fr> CC: Randy MacLeod <randy.macleod@windriver.com> (From OE-Core rev: 374a91204bdaf44067f6b0ae89ed60934751efaa) Signed-off-by: Christos Gavros <gavrosc@yahoo.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* boost: Use PN/BPN for naming of packagesAlex Kiernan2025-03-031-12/+7
| | | | | | | | | | | | | | | | | | Rework the anon Python so that it doesn't expect to find non-MLPREFIXed FILES overrides which are then mapped into MLPREFIXed versions, this allows the apparent hardcoding of boost-{test,serialization} to be written more naturally (and is significantly less surprising). With this, and a change to lookup ${BPN} when generating split package names, generating an explicitly versioned boost package (e.g. "boost-1.82") alongside the main boost package ("boost") can be done by copying/renaming the older recipe. This is useful when upstream code hasn't yet been ported to newer boost and an older version is required. (From OE-Core rev: b0770990a8b332dd2de802091164c9506882a465) Signed-off-by: Alex Kiernan <alex.kiernan@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tcmode-default: bump GOVERSION to 1.24.0hongxu2025-03-031-1/+1
| | | | | | | | | | | | | | Due to we have upgraded go to 1.24.0, we should also bump GOVERSION to fix preferred version warning ... WARNING: preferred version 1.22% of go not available (for item go) WARNING: versions of go available: 1.24.0 ... (From OE-Core rev: 939449cfcb4a920132145d2ad1212bac3acb1baa) Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* go: remove support for GOROOT_FINALHongxu Jia2025-03-032-2/+0
| | | | | | | | | | | | | | | | | After upstream go applied commit [cmd: remove support for GOROOT_FINAL][1], GOROOT_FINAL variable is dropped and use option -trimpath to instead [2] The option -trimpath has already been added to GOBUILDFLAGS in go.bbclass [1] https://github.com/golang/go/commit/507d1b22f4b58ac68841582d0c2c0ab6b20e5a98 [2] https://github.com/golang/go/issues/62047 (From OE-Core rev: 791ab77ac05f658ecd61525a3d9b1afaf8ac6e06) Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* go: fix buildpath issue for go-runtimeHongxu Jia2025-03-033-1/+53
| | | | | | | | | | | | | | | | | | | | | | | In upstream commit [cmd: remove support for GOROOT_FINAL][1], it clear GOROOT for func ld when -trimpath is used But it missed to do the same thing for share libarary linking which caused building go-runtime failed with buildpath issue |ERROR: go-runtime-1.23.4-r0 do_package_qa: QA Issue: File /usr/lib/go/pkg/ linux_amd64_dynlink/libstd.so in package go-runtime contains reference to TMPDIR [buildpaths] This commit applied a patch to clear GOROOT for func ldShared when -trimpath is used and add option -trimpath to go-runtime build [1] https://github.com/golang/go/commit/507d1b22f4b58ac68841582d0c2c0ab6b20e5a98 [2] https://github.com/golang/go/commit/507d1b22f4b58ac68841582d0c2c0ab6b20e5a98#diff-cab5921f94f2667bb0bc1b935d2d46b4c03541b4351b33438ab7290b94dea212R669 (From OE-Core rev: f7b05ebfdc6504a8360741f273163ef7fbb11b10) Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* go: upgrade 1.22.12 -> 1.24.0Hongxu Jia2025-03-0317-90/+135
| | | | | | | | | | | | | | | | Refresh patches See [1] for Go 1.24 Release Notes License-Update: update per Google Legal [2] [1] https://go.dev/doc/go1.24 [2] https://github.com/golang/go/commit/760b722c344d312ab62a5c2f94865a869ce0bab9 (From OE-Core rev: fc6625e934d9b098359103c82cdbcd0c7ce6caee) Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildstats: Avoid rare UnboundLocalErrorRichard Purdie2025-03-031-6/+9
| | | | | | | | | | | | In rare cases BUILDNAME can seemingly be None outside of heartbeat events which leads to UnboundLocalErrors as bsdir and taskdir aren't defined. Skip the code in these cases rather than generate tracebacks which cause bitbake server to exit. (From OE-Core rev: 0f74d804ba0daf7e8bd6481597740b9d89821414) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* shadow-native: Disable syslog usageRichard Purdie2025-03-032-0/+23
| | | | | | | | | | | | Spamming the build host's syslog with useradd information during image creation isn't great. Add a patch to disable that. It may be possible to convince upstream to make it a configure option but for now the patch is trivial and reduces host impact to the logs. (From OE-Core rev: a52572886e60e4aff9d54b57bf45a301e1dec1ee) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cml1.bbclass: use consistent make flags for menuconfigEnrico Jörns2025-03-032-4/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The class called 'make menuconfig' without any of the make variables and options set in EXTRA_OEMAKE, resulting in a quite different build environment than actually intended. For the kernel.bbclass this was fixed in commit 8c616bc0 ("kernel: Use consistent make flags for menuconfig") by appending ${EXTRA_OEMAKE} to KCONFIG_CONFIG_COMMAND. Instead of fixing this individually for additional recipes, we simply include ${EXTRA_OEMAKE} in KCONFIG_CONFIG_COMMAND by default. For most class users, this change is directly visible in the generated .config file: * For barebox and u-boot, the CONFIG_GCC_VERSION erroneously reflected the host GCC version before where it now correctly reflects the target toolchain's GCC. * For u-boot, also the "Compiler: " line at the beginning of the .config now prints the target toolchain instead of the host ones. * The kernel had this already set. * busybox did not produce any difference. Note that these projects might base some compile-time decisions on e.g. the actual compiler version used. Having the wrong one in the menuconfig-generated .config affects at least the visibility and consistency. Reported-by: Ulrich Ölmann <u.oelmann@pengutronix.de> (From OE-Core rev: 1b6ddd452837e67b500a84455a234f5edc8250a9) Signed-off-by: Enrico Jörns <ejo@pengutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* boost: add charconv libMarkus Volk2025-03-031-0/+1
| | | | | | | | | | | | | | | In boost 1.85 a charconv implementation in c++11 was added [https://www.boost.org/doc/libs/master/libs/charconv/doc/html/charconv.html] This is already used in real life and e.g. building the current wesnoth release fails with: | /usr/src/debug/wesnoth/1.19.9/src/utils/charconv.hpp:57:(.text+0x238b): undefined reference to `boost::charconv::to_chars(char*, char*, double, boost::charconv::chars_format)' Add charconv to BOOST_LIBS to provide the library (From OE-Core rev: 42d14c130f2159c1d9ea314acc93142e6ccb2761) Signed-off-by: Markus Volk <f_l_k@t-online.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* xwayland: upgrade 24.1.5 -> 24.1.6Vijay Anusuri2025-03-031-1/+1
| | | | | | | | | | | | | | | | | | | | | Includes security fix * CVE-2025-26594 * CVE-2025-26595 * CVE-2025-26596 * CVE-2025-26597 * CVE-2025-26598 * CVE-2025-26599 * CVE-2025-26600 * CVE-2025-26601 Ref: https://lists.x.org/archives/xorg-announce/2025-February/003584.html https://lists.x.org/archives/xorg-announce/2025-February/003586.html (From OE-Core rev: c3f99b156a94e6687f2a6221a88d463730fd7561) Signed-off-by: Vijay Anusuri <vanusuri@mvista.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libbsd: Remove package specific licensesPeter Kjellerstedt2025-03-031-9/+2
| | | | | | | | | | | | After the removal of BSD-4-Clause from LICENSE in commit 362435b0aec (libbsd: Drop licenses that were removed upstream), the licenses for all packages match the licenses for the recipe. Thus there is no longer any reason to explicitly specify the package licenses. (From OE-Core rev: 0c1b68fefe41d92eaa87578ff644bc254e078f9a) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* automake: remove upstreamed patchesRoss Burton2025-03-033-96/+0
| | | | | | | | | | | | | | | | 0001-automake-Add-default-libtool_tag-to-cppasm.patch was upstreamed in 1.16[1]. 0003-build-fix-race-in-parallel-builds.patch wasn't directly applied, but a fix for the same problem was merged in 1.17[2]. [1] automake dc67b18d "automake: Add default libtool_tag to cppasm" [2] automake 5d022858 "build: fix race in parallel builds" (From OE-Core rev: 386feebe8221c5ef0f87d371dc3e79bfdee1a3bb) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ltp: upgrade 20240930 -> 20250130Yi Zhao2025-03-032-45/+5
| | | | | | | | | | | * Drop 0001-sched_attr-Do-not-define-for-glibc-2.41.patch as it has been merged upstream. * Skip statmount02 case which does not work on musl. (From OE-Core rev: 5d72185e65aa0d9012913d9d095caceada7799d7) Signed-off-by: Yi Zhao <yi.zhao@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Revert "cve-update-nvd2-native: Tweak to work better with NFS DL_DIR"Peter Marko2025-03-011-2/+0
| | | | | | | | | | | | This reverts commit 7adaec468d3a61d88c990b1b319b34850bee7e44. It does not seem to fix the issue it was supposed to fix. Additionally it breaks code which decides in full/partial update, because it manipulates timestamp that code is relying on. (From OE-Core rev: ebc65fdddd7ce51f0f1008baa30d0ae7918ae0bb) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rust-llvm: Fix build break found with clangKhem Raj2025-02-282-1/+33
| | | | | | | | | | call and callee have mismatched types, this patch fixes it (From OE-Core rev: 88e5970998fb4c72844056be19e3a9f77de3f4d6) Signed-off-by: Khem Raj <raj.khem@gmail.com> Cc: Randy MacLeod <Randy.MacLeod@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* psplash: ignore startup errors in psplash-systemd.serviceMikko Rapeli2025-02-281-1/+2
| | | | | | | | | | | | | | | | psplash-systemd.service depends on FIFO created by psplash-start@fb0.service. This FIFO can be removed due to signals or /dev/fb0 related errors when psplash-start@fb0.service exits. This exit can happen when psplash-systemd.service is being started. Thus ignore all errors in psplash-systemd.service startup. There are too many ways things can go wrong and all of them leave open race conditions unless a single process handles all of the psplash usecases including progress bar updates. (From OE-Core rev: 580ae81e102bf999cb89f05430c737210253d90a) Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2025-08-08 03:46:17 +0000