[pull] master from buildroot:master#867
Merged
pull[bot] merged 16 commits intomir-one:masterfrom Feb 14, 2026
Merged
Conversation
The patch: * bumps Linux kernel to version 6.18.8 * bumps U-Boot to version 2026.01 Signed-off-by: Giulio Benetti <[email protected]> [Julien: change linux.hash comment to use hash from upstream] Signed-off-by: Julien Olivain <[email protected]>
The patch: * bumps Linux kernel to version 6.18.8 * bumps U-Boot to version 2026.01 * forces check hashes Signed-off-by: Giulio Benetti <[email protected]> [Julien: change linux.hash comment to use hash from upstream] Signed-off-by: Julien Olivain <[email protected]>
The patch: * bumps Linux kernel to version 6.18.8 * bumps U-Boot to version 2026.01 * forces check hashes Signed-off-by: Giulio Benetti <[email protected]> [Julien: change linux.hash comment to use hash from upstream] Signed-off-by: Julien Olivain <[email protected]>
The patch: * bumps Linux kernel to version 6.18.8 * bumps U-Boot to version 2026.01 * forces check hashes Signed-off-by: Giulio Benetti <[email protected]> [Julien: change linux.hash comment to use hash from upstream] Signed-off-by: Julien Olivain <[email protected]>
The patch: * bumps Linux kernel to version lf-6.12.49-2.2.0 * bumps U-Boot to version lf-6.12.49-2.2.0 Signed-off-by: Giulio Benetti <[email protected]> Signed-off-by: Julien Olivain <[email protected]>
The patch: * bumps Linux kernel to version 6.18.8 * bumps U-Boot to version 2026.01 * forces check hashes Signed-off-by: Giulio Benetti <[email protected]> [Julien: change linux.hash comment to use hash from upstream] Signed-off-by: Julien Olivain <[email protected]>
… 2026.01 The patch: * bumps Linux kernel to version 6.18.8 * bumps U-Boot to version 2026.01 * forces check hashes * switches to extlinux Signed-off-by: Giulio Benetti <[email protected]> [Julien: - change linux.hash comment to use hash from upstream - add "_lime" in commit title ] Signed-off-by: Julien Olivain <[email protected]>
The patch: * bumps Linux kernel to version 6.18.8 * bumps U-Boot to version 2026.01 * forces check hashes * switches to extlinux Signed-off-by: Giulio Benetti <[email protected]> [Julien: change linux.hash comment to use hash from upstream] Signed-off-by: Julien Olivain <[email protected]>
This commit also updates olimex_a20_olinuxino_lime_defconfig olimex_a20_olinuxino_lime2_defconfig to use this new rootfs_overlay_mali directory. This is to differentiate for the upcoming patch for a20_olinuxino_micro_defconfig Signed-off-by: Giulio Benetti <[email protected]> [Julien: add extra info in commit log] Signed-off-by: Julien Olivain <[email protected]>
…o 2026.01 The patch: * bumps Linux kernel to version 6.18.8 * bumps U-Boot to version 2026.01 * forces check hashes * switches to extlinux Signed-off-by: Giulio Benetti <[email protected]> [Julien: change linux.hash comment to use hash from upstream] Signed-off-by: Julien Olivain <[email protected]>
The patch: * bumps Linux kernel to version 6.18.8 * bumps U-Boot to version 2026.01 * forces check hashes * switches to extlinux Signed-off-by: Giulio Benetti <[email protected]> [Julien: change linux.hash comment to use hash from upstream] Signed-off-by: Julien Olivain <[email protected]>
The patch: * bumps Linux kernel to version 6.18.8 * bumps U-Boot to version 2026.01 * bumps ATF to version 2.14.0 * forces check hashes * switches to extlinux Signed-off-by: Giulio Benetti <[email protected]> [Julien: change linux.hash comment to use hash from upstream] Signed-off-by: Julien Olivain <[email protected]>
libxmslec1 build fails on some configurations with the following build
logs:
CC libxmlsec1_openssl_la-kw_des.lo
kw_des.c:75:8: error: unknown type name 'xmlSecKWDes3Klass'; did you mean 'xmlSecKWAesKlass'?
75 | static xmlSecKWDes3Klass xmlSecOpenSSLKWDes3ImplKlass = {
| ^~~~~~~~~~~~~~~~~
| xmlSecKWAesKlass
kw_des.c:77:5: error: initialization of 'int' from 'int (*)(struct _xmlSecTransform *, xmlSecByte *, size_t, size_t *)' {aka 'int (*)(struct _xmlSecTransform *, unsigned char *, long unsigned int, long unsigned int *)'} makes integer from pointer without a cast [-Wint-conversion]
77 | xmlSecOpenSSLKWDes3GenerateRandom, /* xmlSecKWDes3GenerateRandomMethod generateRandom; */
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
kw_des.c:77:5: note: (near initialization for 'xmlSecOpenSSLKWDes3ImplKlass')
kw_des.c:77:5: error: initializer element is not computable at load time
kw_des.c:77:5: note: (near initialization for 'xmlSecOpenSSLKWDes3ImplKlass')
kw_des.c:78:5: error: excess elements in scalar initializer
78 | xmlSecOpenSSLKWDes3Sha1, /* xmlSecKWDes3Sha1Method sha1; */
| ^~~~~~~~~~~~~~~~~~~~~~~
kw_des.c:78:5: note: (near initialization for 'xmlSecOpenSSLKWDes3ImplKlass')
kw_des.c:79:5: error: excess elements in scalar initializer
79 | xmlSecOpenSSLKWDes3BlockEncrypt, /* xmlSecKWDes3BlockEncryptMethod encrypt; */
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
kw_des.c:79:5: note: (near initialization for 'xmlSecOpenSSLKWDes3ImplKlass')
kw_des.c:80:5: error: excess elements in scalar initializer
80 | xmlSecOpenSSLKWDes3BlockDecrypt, /* xmlSecKWDes3BlockDecryptMethod decrypt; */
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[...]
This build failure is due to those struct definitions being set
conditionally in src/kw_aes_des.h behind a XMLSEC_NO_DES define, and
this define ending up being 1 on some builds. We could assume that the
makefiles in libxmlsec should just not try to build any DES related file
when XMLSEC_NO_DES is set to 1 (and so, in this specific case, not try
to build src/openssl/kw_des.c), but the autotools tooling in the project
is not the one setting XMLSEC_NO_DES: there is a mismatch between
detected features at configure time and build time.
- at build time, the tooling just checks if user has passed
`--enable-des=no`. If so, it sets XMLSEC_NO_DES, otherwise it assumes
that DES support is available.
- at build time, libxmlsec tries to build openssl backend. This backend
checks OpenSSL features, especially whether OPENSSL_NO_DES is set (and
if so, it enforces XMLSEC_NO_DES to 1 as well)
- This OPENSSL_NO_DES comes from libopenssl configuration headers
installed in sysroot. Its presence is driven by the `no-des` option
passed at libopenssl configure time
- This `no-des` flag is driven by buildroot option
BR2_PACKAGE_LIBOPENSSL_ENABLE_DES
There are multiple options to fix this package here:
1. fixing upstream package to make the features detection more robust (eg
check openssl headers at configure time to ensure that DES is
supported)
2. enforce XMLSEC_NO_DES if BR2_PACKAGE_LIBOPENSSL_ENABLE_DES is not set
3. systematically enforce XMLSEC_NO_DES=1
Now:
- 1 may take time, and would then need a temporary patch to live in
buildroot while the fix is accepted upstream and released
- 2 works only for libopenssl, what if libressl is used ?
- DES usage is discouraged anyway, as stated by configure logs:
[...]
checking for DES support... yes (use discouraged)
[...]
As the package has been introduced very recently, there's a very low
chance to break any user use case by completely disabling DES support.
Systematically disable DES support in libxmlsec1 to discourage usage and
fix build failure when the corresponding SSL library does not expose DES
support.
Fixes: https://autobuild.buildroot.org/results/3e15f03dc0211c622125ebb69ff7230ce900029a/
Signed-off-by: Alexis Lothoré <[email protected]>
Signed-off-by: Julien Olivain <[email protected]>
Changelog: https://github.com/Canop/broot/blob/v1.55.0/CHANGELOG.md Signed-off-by: Alexander Shirokov <[email protected]> Signed-off-by: Julien Olivain <[email protected]>
https://github.com/libimobiledevice/libplist/blob/2.7.0/NEWS Signed-off-by: Bernd Kuhls <[email protected]> Signed-off-by: Julien Olivain <[email protected]>
https://lore.freedesktop.org/wayland-devel/aY56u6fqOsHIZJXx@quokka/T/#u Signed-off-by: Bernd Kuhls <[email protected]> Signed-off-by: Julien Olivain <[email protected]>
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 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 : )