[pull] master from buildroot:master #414
Merged
Conversation
This file contains 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
![pull[bot]](https://avatars.githubusercontent.com/in/12910?s=60&v=4){kind=small}
Signed-off-by: Bernd Kuhls <[email protected]> Signed-off-by: Julien Olivain <[email protected]>
Signed-off-by: Bernd Kuhls <[email protected]> Signed-off-by: Julien Olivain <[email protected]>
directfb.org is dead so since commit 89ab2a5 (from 2022), we are downloading from sources.buildroot.net. Clearly DirectFB 1.x is no longer maintained. A DirectFB 2.x project is now at https://github.com/directfb2/, but despite an attempt in August 2024 [1], it still isn't packaged in Buildroot. Therefore it's time to drop directfb 1.x, which doesn't prevent in the future from adding directfb 2.x. [1] https://lore.kernel.org/buildroot/[email protected]/ Signed-off-by: Thomas Petazzoni <[email protected]> Signed-off-by: Julien Olivain <[email protected]>
directfb.org is dead, and DirectFB is no longer maintained, so drop this package. Note that we are removing BR2_PACKAGE_DIRECTFB_MULTI in this commit, without adding a Config.in.legacy entry, because a follow-up commit will remove BR2_PACKAGE_DIRECTFB entirely. Fixes: http://autobuild.buildroot.net/results/f8bc1d09f15362dc60656b517f36efb7ed5cbd1b/ Signed-off-by: Thomas Petazzoni <[email protected]> Signed-off-by: Julien Olivain <[email protected]>
As we're about to remove DirectFB due to it no longer being maintained, we need to first remove Lite, a toolbox based on DirectFB. Signed-off-by: Thomas Petazzoni <[email protected]> Signed-off-by: Julien Olivain <[email protected]>
As we're about to remove the DirectFB package, let's drop DirectFB support in links. Signed-off-by: Thomas Petazzoni <[email protected]> Signed-off-by: Julien Olivain <[email protected]>
As we're about to remove the DirectFB package, let's drop the GStreamer DirectFB plugin. Signed-off-by: Thomas Petazzoni <[email protected]> Signed-off-by: Julien Olivain <[email protected]>
As we're about to remove the DirectFB package, let's drop the DirectFB graphics backend in Qt5. Signed-off-by: Thomas Petazzoni <[email protected]> Signed-off-by: Julien Olivain <[email protected]>
As we're about to remove the DirectFB package, let's drop DirectFB support in sdl. Signed-off-by: Thomas Petazzoni <[email protected]> Signed-off-by: Julien Olivain <[email protected]>
As we're about to remove the DirectFB package, let's drop DirectFB support in sdl2. Signed-off-by: Thomas Petazzoni <[email protected]> Signed-off-by: Julien Olivain <[email protected]>
As we're about to remove the DirectFB package, let's drop DirectFB support in tekui. Signed-off-by: Thomas Petazzoni <[email protected]> Signed-off-by: Julien Olivain <[email protected]>
As we're about to remove the DirectFB package, let's drop DirectFB support in vulkan-loader. Signed-off-by: Thomas Petazzoni <[email protected]> Signed-off-by: Julien Olivain <[email protected]>
As we're about to remove the DirectFB package, let's drop DirectFB support in vulkan-tools. Signed-off-by: Thomas Petazzoni <[email protected]> Signed-off-by: Julien Olivain <[email protected]>
directfb.org is dead so since commit 89ab2a5 (from 2022), we are downloading from sources.buildroot.net. Clearly DirectFB 1.x is no longer maintained. A DirectFB 2.x project is now at https://github.com/directfb2/, but despite an attempt in August 2024 [1], it still isn't packaged in Buildroot. Therefore it's time to drop directfb 1.x, which doesn't prevent in the future from adding directfb 2.x. [1] https://lore.kernel.org/buildroot/[email protected]/ Signed-off-by: Thomas Petazzoni <[email protected]> Signed-off-by: Julien Olivain <[email protected]>
Version 0.23.16 change log:
* database
- fix integer overflows with 64-bit inode numbers
* filter
- ffmpeg: fix for filters producing no output
* support libfmt 11
* support ICU 76
Adapt 0001-src-event-meson.build-add-atomic-dependency-for-spar.patch to
silence check-package warnings
Remove 0002-lib-fmt-support-build-with-libfmt-11.0.0.patch, changes were
applied upstream
$ utils/check-package package/mpd/*
916 lines processed
0 warnings generated
$ echo "BR2_PACKAGE_MPD=y" > ~/output/mpd.config
$ utils/test-pkg -c ~/output/mpd.config -d ~/output -p mpd
bootlin-armv5-uclibc [1/6]: OK
bootlin-armv7-glibc [2/6]: OK
bootlin-armv7m-uclibc [3/6]: SKIPPED
bootlin-x86-64-musl [4/6]: OK
br-arm-full-static [5/6]: OK
arm-aarch64 [6/6]: OK
6 builds, 1 skipped, 0 build failed, 0 legal-info failed, 0 show-info failed
Signed-off-by: Andreas Ziegler <[email protected]>
Signed-off-by: Thomas Petazzoni <[email protected]>
Signed-off-by: Francois Perrad <[email protected]> Signed-off-by: Thomas Petazzoni <[email protected]>
Signed-off-by: Francois Perrad <[email protected]> Signed-off-by: Thomas Petazzoni <[email protected]>
Signed-off-by: Francois Perrad <[email protected]> Signed-off-by: Thomas Petazzoni <[email protected]>
Building on a s390x host, we currently end up with:
output/host/lib
output/host/lib32 -> lib
output/host/lib64
host-libopenssl installs to lib64, but since the kernel build doesn't
explicitly search there, it breaks:
>>> linux 6.6.32 Building
[...]
HOSTCC scripts/sign-file
/usr/bin/ld: cannot find -lcrypto: No such file or directory
collect2: error: ld returned 1 exit status
Fix this by creating a lib64 link instead of lib32, so we get:
output/host/lib
output/host/lib64 -> lib
Signed-off-by: Reza Arbab <[email protected]>
Signed-off-by: Thomas Petazzoni <[email protected]>
* disable junction and nfsdctl by default * drop 2 local patches that have been committed. Signed-off-by: Giulio Benetti <[email protected]> Reviewed-by: Petr Vorel <[email protected]> Signed-off-by: Thomas Petazzoni <[email protected]>
Signed-off-by: Giulio Benetti <[email protected]> Reviewed-by: Petr Vorel <[email protected]> Signed-off-by: Thomas Petazzoni <[email protected]>
For change logs since 2.0.18, see: https://github.com/numactl/numactl/releases/tag/v2.0.19 This commit also removes the package patch, which is included in this version. Signed-off-by: Julien Olivain <[email protected]> Signed-off-by: Thomas Petazzoni <[email protected]>
This is a basic test for Xvisor RISC-V 64bit. It is running few management and status commands. It does not start a Linux kernel. RISC-V 64bit was chosen for this test because it was the simplest solution to run xvisor in a qemu emulator. Signed-off-by: Julien Olivain <[email protected]> Signed-off-by: Thomas Petazzoni <[email protected]>
opkg configure script supports the --with-libsolv option since v0.3.2. See [1]. Note that the opkg internal satisfaction solver is beeing deprecated as of v0.7.0. See the note in changelog [2]. [1] https://git.yoctoproject.org/opkg/commit?id=bc2d3413e7dd61dd0001cc30b7785880c26eada4 [2] https://git.yoctoproject.org/opkg/tree/CHANGELOG.md?h=v0.7.0#n12 Signed-off-by: Julien Olivain <[email protected]> Signed-off-by: Thomas Petazzoni <[email protected]>
This commit adds the Cortex-A78 core, which is a armv8.2a ISA. See: [1] [2]. This CPU support was added in GCC 11. See [3] [4]. Buildroot commit 771da1d "configs/nvidia_bf3_defconfig: new defconfig" [5] added the first defconfig for a board including this CPU. [1] https://developer.arm.com/Processors/Cortex-A78 [2] https://developer.arm.com/documentation/101430/0102/Functional-description/Introduction/About-the-core [3] https://gcc.gnu.org/gcc-11/changes.html [4] https://gcc.gnu.org/git/?p=gcc.git;a=blob;f=gcc/config/aarch64/aarch64-cores.def;hb=releases/gcc-11.1.0#l98 [5] https://gitlab.com/buildroot.org/buildroot/-/commit/771da1dd9b209adfb27d2dd344a4b2fdcc8bacc4 Signed-off-by: Julien Olivain <[email protected]> Signed-off-by: Thomas Petazzoni <[email protected]>
Signed-off-by: Julien Olivain <[email protected]> Signed-off-by: Thomas Petazzoni <[email protected]>
Release notes: https://lists.x.org/archives/xorg-announce/2024-March/003495.html Signed-off-by: Raphael Pavlidis <[email protected]> Signed-off-by: Thomas Petazzoni <[email protected]>
Upstream changelog: https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?h=5.79&id=0845b8f6ef2ac004b1c953cf4fe4ca3458cd8e36 Patch for musl compatibility taken from upstream "master". Signed-off-by: Fiona Klute (WIWA) <[email protected]> Signed-off-by: Thomas Petazzoni <[email protected]>
Since D-Bus 1.14.0 installing default policies into sysconfdir (/etc) is deprecated, they should go into datadir (/usr/share) instead [1]. Follow that policy. [1] https://gitlab.freedesktop.org/dbus/dbus/-/blob/8f1e00427f7048f8b24c3a1cfca8903254fe00d4/NEWS#L274-283 Signed-off-by: Fiona Klute (WIWA) <[email protected]> Signed-off-by: Thomas Petazzoni <[email protected]>
The datafiles include the dbus policy, without which bluetoothd fails to start (unless it is provided by other means): # /usr/libexec/bluetooth/bluetoothd -n bluetoothd[1011]: Bluetooth daemon 5.78 D-Bus setup failed: Connection ":1.7" is not allowed to own the service "org.bluez" due to security policies in the configuration file bluetoothd[1011]: src/main.c:main() Unable to get on D-Bus The installation issue 1a8676a was meant to fix is the result of upstream incorrectly installing /etc/bluetooth with 0555 (strictly read-only) permissions. Fixes: 1a8676a Signed-off-by: Fiona Klute (WIWA) <[email protected]> Signed-off-by: Thomas Petazzoni <[email protected]>
* use long-form options * consistently use start-stop-daemon with --exec * wait for process to be gone and delete PID file on stop Signed-off-by: Fiona Klute (WIWA) <[email protected]> Signed-off-by: Thomas Petazzoni <[email protected]>
Release notes: https://github.com/google/flatbuffers/releases/tag/v24.12.23 Signed-off-by: Bernd Kuhls <[email protected]> Signed-off-by: Thomas Petazzoni <[email protected]>
Signed-off-by: Bernd Kuhls <[email protected]> Signed-off-by: Thomas Petazzoni <[email protected]>
Signed-off-by: Bernd Kuhls <[email protected]> Signed-off-by: Thomas Petazzoni <[email protected]>
Changelog: https://www.php.net/ChangeLog-8.php#PHP_8_3 Release notes: https://news-web.php.net/php.announce/448 Signed-off-by: Bernd Kuhls <[email protected]> Signed-off-by: Thomas Petazzoni <[email protected]>
See release announce: https://octave.org/news/release/2024/12/15/octave-9.3.0-released.html Signed-off-by: Julien Olivain <[email protected]> Signed-off-by: Thomas Petazzoni <[email protected]>
Since procps-ng was bumped from 3.3.17 to 4.0.4 in commit d79f40d ("package/procps-ng: security bump to version 4.0.4"), the build has been failing on !wchar configurations with: src/ps/output.c:68:10: fatal error: wctype.h: No such file or directory 68 | #include <wctype.h> | ^~~~~~~~~~ compilation terminated. The problematic code has been added by upstream commit https://gitlab.com/procps-ng/procps/-/commit/605ea4a8f7460920b6de9e432757bd13f80f0dba, which landed in upstream release v4.0.0. To solve this, we simply add a BR2_USE_WCHAR dependency, and update the comment related to this dependency on the only reverse dependency of procps-ng. Fixes: http://autobuild.buildroot.net/results/afc035e866bec6f2c14f9d52fa74a9c1897706de/ Signed-off-by: Thomas Petazzoni <[email protected]> Signed-off-by: Julien Olivain <[email protected]>
Patch 0001 is dropped as it's upstream as of ca004d4657d5e8b468a4552ede429be53193a3a9. Patch 0002 is dropped as it's upstream as of 263fe04f9ed6f3f40fdb7ce249221e03dc926c9b. Patch 0003 is dropped as it's upstream as of 2507bc475782ff5e0541d37c780dff1e293c9553. Patch 0004 is dropped as it's upstream as of 587efb47df7ddbfda4e6abdd1e7792a2531a238f. Patch 0005 is dropped as it's upstream as of 5acbb5dc1587d688de646d739a97251eb893bbb0. Therefore AUTORECONF = YES can be dropped as we're no longer patching the package. Release notes: https://gitlab.com/procps-ng/procps/-/releases/v4.0.5 Signed-off-by: Thomas Petazzoni <[email protected]> Signed-off-by: Julien Olivain <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.1)
Can you help keep this open source service alive? 💖 Please sponsor : )