[pull] master from buildroot:master #848
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When running "make pkg-stats" on a host with Python 3.14 (e.g.
Fedora 43 for example), the execution fails with the error:
Checking URL status
Traceback (most recent call last):
File "/buildroot/support/scripts/pkg-stats", line 1387, in <module>
__main__()
~~~~~~~~^^
File "/buildroot/support/scripts/pkg-stats", line 1368, in __main__
loop = asyncio.get_event_loop()
File "/usr/lib64/python3.14/asyncio/events.py", line 715, in get_event_loop
raise RuntimeError('There is no current event loop in thread %r.'
% threading.current_thread().name)
RuntimeError: There is no current event loop in thread 'MainThread'.
This is due to a breaking change introduced in Python 3.14
asyncio.get_event_loop(). See [1]. Before Python 3.14, this call was
creating and setting an event loop if there was none. This situation
is now a runtime error.
In order to fix this issue with newer Python version, while keeping
backward compatibility, this commit replaces the code:
loop = asyncio.get_event_loop()
by an explicit event loop creation:
loop = asyncio.new_event_loop()
asyncio.set_event_loop(loop)
This commit was tested on a Fedora 43 host with Python-3.14.2, and
with the Buildroot Docker image plus the python3-aiohttp package
which is a Debian 12 with Python-3.11.2.
[1] https://docs.python.org/3.14/library/asyncio-eventloop.html#asyncio.get_event_loop
Signed-off-by: Julien Olivain <ju.o@free.fr>
Tested-by: Vincent Fazio <vfazio@xes-inc.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
…ORE_CVES Commit [1] bumped glibc from 2.42-3-gbc13db739 to 2.42-51-gcbf39c26b to fix some CVEs, but forgot to add those CVEs to GLIBC_IGNORE_CVES. This was needed because the GLIBC_CPE_ID_VERSION used for CVE checks remains to the same value "2.42" which is marked as vulnerable to those CVEs. This commit adds those _IGNORE_CVES with the corresponding upstream commit references, to make sure they will not be reported by the "make pkg-stats" command. Fixes: - [1] [1] https://gitlab.com/buildroot.org/buildroot/-/commit/18de297a5ad3d1fc1b44f54ae69289ca10200ad5 Cc: Waldemar Brodkorb <wbx@openadk.org> Cc: Thomas Perale <thomas.perale@mind.be> Signed-off-by: Julien Olivain <ju.o@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
…_RPCDB Package xinetd requires libtirpc rpcdb option enabled since the bump of libtirpc to version 1.3.7 with buildroot commit 3f3d6e4 which includes upstream commit: https://git.linux-nfs.org/?p=steved/libtirpc.git;a=commit;h=7cea8ad66aecc21e6caae330b5d31075af399193 Fixes: https://autobuild.buildroot.net/results/4db/4db625d395f38636b67adbbf6286c6c9da155f62/ Signed-off-by: Bernd Kuhls <bernd@kuhls.net> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Since commit [1] (core/pkg-cmake: provide our own platform
description), Buildroot is setting its own CMake platform
description. This description applies minor changes on top of
the CMake Linux platform, see [2] and [3]. The CMake system specific
script tries to include an initialization script, if present.
See [4].
Since in commit [1] we set the CMAKE_SYSTEM_NAME to "Buildroot"
(rather than "Linux"), CMake will search for a
"Platform/Buildroot-Initialize.cmake" which does not exist, and
continue normally, since the include is optional.
The "Platform/Linux-Initialize.cmake" file is the one setting the
LINUX [6] and UNIX [7] variables, which are expected to be true on
a linux compatible system. In Buildroot, it is currently not
included, so those variables are unset.
If a CMake package in Buildroot has a construct such as:
if(LINUX)
# ...do things...
else()
message(FATAL_ERROR "System not supported")
endif()
It will fail at configuration time.
This situation happened when trying to add the btop++ package
in Buildroot. See [8].
Since the initial intent of commit [1] was to make the Buildroot
CMake system inherit from Linux plus some fixups, this commit simply
adds a Buildroot-Initialize.cmake file that includes the
Linux-Initialize.cmake one from CMake. This will have the effect
to properly define the LINUX and UNIX variables.
[1] https://gitlab.com/buildroot.org/buildroot/-/commit/c69b14fe2f72d8134057b115884c04a2bf27d410
[2] https://gitlab.com/buildroot.org/buildroot/-/blob/2025.11/support/misc/Buildroot.cmake#L1-4
[3] https://cmake.org/cmake/help/v4.2/variable/CMAKE_SYSTEM_NAME.html
[4] https://gitlab.kitware.com/cmake/cmake/-/blob/v4.2.1/Modules/CMakeSystemSpecificInitialize.cmake#L35
[5] https://gitlab.kitware.com/cmake/cmake/-/blob/v4.2.1/Modules/Platform/Linux-Initialize.cmake
[6] https://cmake.org/cmake/help/v4.2/variable/LINUX.html
[7] https://cmake.org/cmake/help/v4.2/variable/UNIX.html
[8] https://github.com/aristocratos/btop/blob/v1.4.6/CMakeLists.txt#L76
Reported-by: Gilles Talis <gilles.talis@gmail.com>
Signed-off-by: Julien Olivain <ju.o@free.fr>
Tested-by: Gilles Talis <gilles.talis@gmail.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Fixes: https://autobuild.buildroot.net/results/258/2589f75f7415cd1a2fd7cf83c6166c900b03cce0/ Signed-off-by: Bernd Kuhls <bernd@kuhls.net> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Buildroot commit 1b8d7e7 bumped the package to version 23.2.1 that contains the upstream commit https://gitlab.freedesktop.org/mesa/mesa/-/commit/77826e835243291df664ccf2a7b8405287b72387#e65744354fdd7dd38342b138e59e40767cfcdaa9 which causes build errors on aarch64_be. The build error was first seen by the autobuilders with mesa3d-23.3.3: https://autobuild.buildroot.net/results/b62/b62eba2155b080ed02fde774994f2fffc8a6ef51/ according to https://autobuild.buildroot.net/?reason=mesa3d-25.3.4&arch=aarch64_be A backport to LTS branches should be considered. Fixes: https://autobuild.buildroot.net/results/efd/efd07d97df4e0c1ceb07fc26e17898afef5435b9/ Signed-off-by: Bernd Kuhls <bernd@kuhls.net> [Romain: update the link to autobuilders mesa3d & aarch64_be issues] Signed-off-by: Romain Naour <romain.naour@smile.fr>
Currently, the relocate-sdk.sh script scans the whole extracted SDK tree to find instances of paths it needs to replace, which can take a significant amount of time when the SDK is large, particularly relative to the number of files that actually need to change. However, the resulting list only depends on the SDK tarball itself, so we can calculate it at build time and ship it with the tarball so relocate-sdk.sh can use it directly. Testing this on my machine with somewhat IOPS-limited rotating media, the time goes down from: $ time ./relocate-sdk.sh Relocating the buildroot SDK from [...] to [...] ... ./relocate-sdk.sh 5.19s user 26.21s system 9% cpu 5:34.40 total To: $ time ./relocate-sdk.sh Relocating the buildroot SDK from [...] to [...] ... ./relocate-sdk.sh 0.49s user 0.29s system 103% cpu 0.749 total Signed-off-by: Florian Larysch <fl@n621.de> Signed-off-by: Arnout Vandecappelle <arnout@rnout.be>
Commit 105e461 added a patch to fix CMake 4 compatibility, but due to line endings issues the patch doesn't apply properly. This commit fixes the patch so that it does apply as it should. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Buildroot commit f710640 bumped the package to version 3.6.0 that includes upstream commit openssl/openssl@8f24a14 which causes build errors on powerpc64. The upstream commit was also backported to older libopenssl branches: openssl/openssl#28990 (comment) but its first appearance on the buildroot master branch was with said bump to 3.6.0. This patch adds an upstream patch to fix the problem. Fixes: https://autobuild.buildroot.net/results/b28/b286ad40f2240a85b9cd0dc44e089d1d6babd3ea/ Signed-off-by: Bernd Kuhls <bernd@kuhls.net> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Release notes: https://ftp.isc.org/isc/bind9/9.18.44/doc/arm/html/notes.html Changelog: https://ftp.isc.org/isc/bind9/9.18.44/doc/arm/html/changelog.html Fixes CVE-2025-13878. Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
This commit adds the -N/--needs-update option, disabled by default, to list only packages with newer upstream versions. All other packages will be excluded from the HTML or JSON output. Signed-off-by: Kadambini Nema <kadambini.nema@gmail.com> Signed-off-by: Arnout Vandecappelle <arnout@rnout.be>
Adds a new user-configurable string to arch/Config.in.riscv, and in arch/arch.mk.riscv appends it to GCC_TARGET_ARCH. This enables custom extensions/combinations to be easily configured. Signed-off-by: Charlie Jenkins <charlie@rivosinc.com> Reviewed-by: Jesse Taube <Mr.Bossman075@gmail.com> [Arnout: - fix check-package warnings - introduce ARCH_RISV_ISA_EXTRA to simplify stripping of quotes ] Signed-off-by: Arnout Vandecappelle <arnout@rnout.be>
For release notes, see: https://gitlab.winehq.org/wine/wine/-/releases/wine-11.0 The --without-osmesa configure option was removed upstream, in commit [1]. This commit removes the options from _CONF_OPTS. Also, since upstream commit [2], the /usr/bin/wine program became a "tool". It needs to be enabled when cross-compiling. As suggested in [3], this commit adds --enable-tools in WINE_CONF_OPTS. This commit also updates the LICENSE file hash, after year update in [4]. [1] https://gitlab.winehq.org/wine/wine/-/commit/370e7d9a50593077e958f3efcc70254990bfe6f3 [2] https://gitlab.winehq.org/wine/wine/-/commit/6d28db86c9c2559e67a4820175416aff20f7abec [3] https://bugs.winehq.org/show_bug.cgi?id=57847 [4] https://gitlab.winehq.org/wine/wine/-/commit/ab59cc16c56fa7400c2076990b53ea95f6889902 Signed-off-by: Julien Olivain <ju.o@free.fr> Signed-off-by: Marcus Hoffmann <buildroot@bubu1.eu>
Buildroot commit 4769724 bumped the package from 4.9.1 to 5.0.0 which includes a major rewrite of the configure script https://cgit.git.savannah.gnu.org/cgit/screen.git/log/src/configure.ac?h=v.4.9.1 https://cgit.git.savannah.gnu.org/cgit/screen.git/log/src/configure.ac?h=v.5.0.0 By default, screen puts the socket directory in $HOME/.screen, which is not writable when the rootfs is readonly: # screen Cannot access /root/.screen: No such file or directory The --enable-socket-dir option added in upstream commit https://cgit.git.savannah.gnu.org/cgit/screen.git/commit/?id=78a961188f7da528c7cefcc63e07f35f04e69a93 allows to configure this, and actually its default value of /run/screen is sensible, so we fix the problem by simply passing --enable-socket-dir, and rely on its default setting. Fixes: https://gitlab.com/buildroot.org/buildroot/-/issues/123 Signed-off-by: Bernd Kuhls <bernd@kuhls.net> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
There are several use cases for installing additional files in the boot partition that is read by the RPi firmware. - autoboot.txt is an optional configuration file for the RPi firmware [1]. Supporting several autoboot files will enable A/B setups, as using the renameat2() system call with the RENAME_EXCHANGE flag will let users atomically replace one autoboot configuration file with the other. This improves reliability in the case of an update which could potentially be interrupted. - Multiple cmdline.txt files are useful in the context of a new [boot_partition] conditional filter introduced in config.txt in commit [2]. This is useful for A/B systems to have identical BootFS partitions on both slots, and not have to edit the kernel command line to ensure the kernel will load the right rootFS after update of the BootFS. - rpi-firmware contains DTB overlays for many "standard" hats, but a custom hat may require a custom overlay. Although it is possible to install additional files in the boot partition in the post-image script, it is very convenient to be able to use the standard RPi post-image script in board/raspberrypi/post-image.sh. That script looks in $BINARIES_DIR/rpi-firmware, so it is convenient to be able to place additional files there. Add the option BR2_PACKAGE_RPI_FIRMWARE_EXTRA_FILES which is simply a list of files to be copied to $BINARIES_DIR/rpi-firmware, which will eventually end up as the boot partition. Make sure that this is done as the last step of RPI_FIRMWARE_INSTALL_IMAGES_CMDS, so the files can override files installed by earlier steps. [1] https://www.raspberrypi.com/documentation/computers/config_txt.html#autoboot-txt [2] raspberrypi/rpi-eeprom@d50b2b3 Signed-off-by: Olivier Benjamin <olivier.benjamin@bootlin.com> Signed-off-by: Arnout Vandecappelle <arnout@rnout.be>
Bump U-Boot to latest release tag linux4microchip+fpga-2025.10. This includes the latest features and bug fixes. Included is a U-Boot version update from v2023.07 to v2025.07. Signed-off-by: Jamie Gibbons <jamie.gibbons@microchip.com> Signed-off-by: Romain Naour <romain.naour@smile.fr>
Bump Linux to latest release tag linux4microchip+fpga-2025.10. This includes the latest features and bug fixes. Included is a kernel version buump to v6.12.48 and a GPIO driver fix. Signed-off-by: Jamie Gibbons <jamie.gibbons@microchip.com> Signed-off-by: Romain Naour <romain.naour@smile.fr>
Bump U-Boot to latest release tag: linux4microchip+fpga-2025.10. This includes the latest features and bug fixes. Included is a U-Boot version bump to v2025.07. Signed-off-by: Jamie Gibbons <jamie.gibbons@microchip.com> Signed-off-by: Romain Naour <romain.naour@smile.fr>
Bump Linux to latest release tag: linux4microchip+fpga-2025.10. This includes the latest features and bug fixes. Included is a kernel bump to v6.12.48. Signed-off-by: Jamie Gibbons <jamie.gibbons@microchip.com> Signed-off-by: Romain Naour <romain.naour@smile.fr>
With the latest U-Boot update, U-Boot now handles this step in the board setup removing the need to set this from a custom boot script. Remove redundant fdt set command from boot script. Signed-off-by: Jamie Gibbons <jamie.gibbons@microchip.com> Signed-off-by: Romain Naour <romain.naour@smile.fr>
Since the bump of libbsd from 0.11.7 to 0.12.2 in Buildroot commit c555b65, the build of libbsd was broken on uClibc, due to changes in libbsd. In order to fix this, we add a patch (submitted upstream), which is based on a suggestion from libbsd's maintainer, itself based on an initial proposal from Dario Binacchi. Fixes: https://autobuild.buildroot.net/results/384022450a09b7d731e3817c812e30e15187344b/ Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Unfortunately, parts of the library is not very no-MMU friendly atm.
The below check fails due to runbg.c requiring fork().
$ ./utils/test-pkg -c libite.config -p libite
bootlin-armv5-uclibc [1/6]: OK
bootlin-armv7-glibc [2/6]: OK
bootlin-armv7m-uclibc [3/6]: FAILED
bootlin-x86-64-musl [4/6]: OK
br-arm-full-static [5/6]: OK
arm-aarch64 [6/6]: OK
The dependency was introduced in libite v2.6.0, so this patch should
be backported to v2025.02.x.
Fixes:
https://autobuild.buildroot.net/results/6c6fd2ae410a82c44da54ee13a09a38a7ab220c1/
Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Changes: - Fix memory leak in which() on realloc() failure - Fix pidfile() to handle missing trailing slash in prefix path Changes to src/pidfile.c do not affect the licensing terms, but require updating the hash of this file that is used as one of the license files. https://github.com/troglobit/libite/releases/tag/v2.6.2 Signed-off-by: Joachim Wiberg <troglobit@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
https://nvd.nist.gov/vuln/detail/CVE-2025-62291 Signed-off-by: Waldemar Brodkorb <wbx@openadk.org> [Marcus: add comment pointing to patch before _IGNORE_CVES] Signed-off-by: Marcus Hoffmann <buildroot@bubu1.eu>
When given a certificate directory with --with-ca-path, curl doesn't list the files in that directory. Instead, it uses the certificate hash to directly open the requested CA certificate. Therefore, putting a bundle in that directory and removing all the individual certificates is not possible. In order to support use of the bundle, a separate configuration option --with-ca-bundle is needed. With this option, it is possible to remove the individual certificates and include just the bundle, which reduces the size of the root filesystem a bit. Note that the bundle is generated by the ca-certificates package, which also installs the individual certificates and the hash symlinks. It keeps both individual certificates and the bundle in the target. Signed-off-by: Lance Fredrickson <lancethepants@gmail.com> Signed-off-by: Arnout Vandecappelle <arnout@rnout.be>
Buildroot commit 473c940 bumped brotli to version 1.2.0 causing build errors on loongarch64. The build error does not occur with brotli 1.1.0. Fixes: https://autobuild.buildroot.net/results/57f/57f61a5fd17432bba05e4f1865f82cc2f4626d3c/ Signed-off-by: Bernd Kuhls <bernd@kuhls.net> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Fixes: https://autobuild.buildroot.net/results/76d/76d18437241d1281566b76ed1cec2ba99c3532da/ The build error was not introduced by the recent bump to 6.8. The oldest build error with the previous brltty version 6.6 used in buildroot dates back to 2023: https://autobuild.buildroot.net/results/78a/78a7fe6edfb84c2b15fff32aa475c975ecd5bdbc/ and with brltty 6.4 to 2022: https://autobuild.buildroot.net/results/a5b/a5b338ce9865fc7afaecd9b671e6a8f290548374/ Signed-off-by: Bernd Kuhls <bernd@kuhls.net> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
… is set The .mk file currently states: If LWS_MAX_SMP=1, then there is no code related to pthreads compiled in the library. If unset, LWS_MAX_SMP defaults to 32 and a small amount of pthread mutex code is built into the library. However, this is incorrect: when unset, LWS_MAX_SMP is actually set to 1, so mutexes aren't built in. To fix, set it to 32 explicitly when threads are enabled. Why 32? Because https://libwebsockets.org/lws-api-doc-master/html/md_README.coding.html states: You can control the context basic data allocation for multithreading from Cmake using -DLWS_MAX_SMP=, if not given it's set to 32. Signed-off-by: Bart Van Severen <bart.vanseveren@barco.com> Signed-off-by: Thomas Devoogdt <thomas.devoogdt@barco.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
The current generated cJSONConfig.cmake holds hard coded path of libraries and makes it impossible to use in SDKs. Use CMakePackageConfigHelpers and @PACKAGE_INIT@ to make them suit for real environment dynamically. Signed-off-by: Guillaume Chaye <guillaume.chaye@zeetim.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Sometimes asterisk buildsystem decides to remove our own build menuselect stuff for the host. And then fails to run the cross-compiled binary. Add a patch to avoid removal of the menuselect stuff. Fixes: - https://autobuild.buildroot.net/results/5f7/5f76f032ee596e928089b064b01f08adacade47a/ Signed-off-by: Waldemar Brodkorb <wbx@openadk.org> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Although it is possible to configure an AArch64 CPU without support for EL2 in practice all the common AArch64 have supported virtualisation from the start. If we really wanted to be strict we could blacklist known non-EL2 CPUs but AFAICT all the current ones in the config have EL2. I should also note KVM on Arm is deprecated and was removed from the kernel in v6.10. Reviewed-by: Jesse Taube <jesse@rivosinc.com> Reviewed-by: Thomas Huth <huth@tuxfamily.org> Signed-off-by: Alex Bennée <alex.bennee@linaro.org> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
When building system binaries you may not even want TCG support if you are only intending to use KVM. Provide the options so the user can select only what they need. With only KVM selected the QEMU build will generally only build the binary for your target system. We keep TCG support on by default so as not to break existing defconfigs. Signed-off-by: Alex Bennée <alex.bennee@linaro.org> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
…sroot." This reverts commit e57c73b. It shouldn't have been pushed in the first place. We had concerns about the change, and replied to the patch contributor accordingly: https://lore.kernel.org/buildroot/aYNbUNuNUs12ulgB@windsurf/ Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
The ukify tool can be used to create Unified Kernel Images. Signed-off-by: Bram Vlerick <bram.vlerick@openpixelsystems.org> [Arnout: - Remove the target option. - Use enabled/disabled instead of true/false. - Always enable for host build. - Add dependency on host-python-pefile. ] Signed-off-by: Arnout Vandecappelle <arnout@rnout.be>
Upstream is dead, website unreachable, and the use case in 2026 is dubious, so drop the package. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
15 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )