Add a simple test case that imports the module and does a simple
compress decompress routine.
Signed-off-by: Flaviu Nistor <flaviu.nistor@gmail.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Even if there is a 0.7.3 on Pypi, there is no 0.7.3 release on the
project homepage, hence the bump to 0.7.2.
The important change is that since 0.7.0, python-snappy uses
python-cramjam instead of nsappy.
Signed-off-by: Flaviu Nistor <flaviu.nistor@gmail.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
When running tests depending on entropy pool being ready on armv7 (eg:
test_openscap.py, which runs the 'oscap' binary, which tries to get
random bytes, even with simple commands), the test may fail on timeout
due to the entropy pool not being ready; this is confirmed by the test
being blocked until "crng init done" line appears in the kernel logs.
A solution could be to just increase the test timeout to a value large
enough to make sure that the entropy pool will be ready in most cases,
but it may be hard to find a value that fits all use cases, and all
tests depending on entropy being ready would deserve the same fix.
Another solution is to replicate what commit 7acb32dabb
("support/testing: add builtin armv5 kernel 4.19 with entropy") did: it
added the virtio-rng-pci argument to allow the guest machine to use host
entropy. The armv7 kernel used for testing seems to be built with the
relevant virtio configuration to allow a similar pass-through, so pass
virtio-rng-device to armv7 kernel when running tests.
Signed-off-by: Alexis Lothoré <alexis.lothore@bootlin.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
The LGPL v2.1 license file was edit in upstream commit 4225417da2 [1],
which is included in ffmpeg 7.0, and Buildroot commit b68bde5643 [2]
bumped to that version, which made ffmpeg-legal-info fail.
Fixes: b68bde5643
[1] 4225417da2 ("all: apply linter fixes")
4225417da2
[2] b68bde5643 ("package/ffmpeg: bump version to 7.0.3")
b68bde5643
Signed-off-by: Titouan Christophe <titouan.christophe@mind.be>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
ncftp still ships a configure script generated with autoconf 2.13, which
determines whether it is cross compiling by simply trying to run a
trivial program built with $CC, instead of looking at --host/--build.
That heuristic breaks when the build machine is able to execute the
binaries produced by the cross compiler, which is typically the case
when building for x86/x86-64 on an x86-64 machine:
checking whether the C compiler (...) is a cross-compiler... no
configure then takes the AC_TRY_RUN path for the remaining tests. Those
tests link against the target libraries but are executed on the build
machine, so they fail as soon as more than the bare C library is
involved. The most visible victim is the curses detection, which links
the test program against the target libncurses and then runs it:
checking for curses library headers... checking for ncurses.h... yes
checking for curses.h... yes
checking for curses library... no
With no curses library, ncftpbookmarks is silently dropped from the
build and installation later fails with:
install: cannot stat '.../build/ncftp-3.3.0/bin/ncftpbookmarks': No such file or directory
Other checks are mis-detected the same way, e.g. the 64-bit integral
type checks, which end up breaking the build itself:
checking how to scan a 64-bit integral type... cannot scan
io_get.c:763:96: error: expected ')' before 'PRINTF_LONG_LONG'
So add a patch making the generated configure script follow what
autoconf has been doing since 2.50, and consider the build cross
compilation as soon as --host is given and differs from --build,
regardless of whether the produced binaries happen to be runnable.
Regenerating configure instead is not an option: the macros in
autoconf_local/aclocal.m4 rely on autoconf 2.13 internals (AC_LANG used
as a value, AC_FD_CC, __oline__, ...) and upstream generates configure
with a patched autoconf 2.13 (see autoconf_local/acgeneral-2.13.m4.patch
and acspecific-2.13.m4.patch). A modern autoconf fails with:
configure.in:53: error: AC_LANG: unknown language:
This regression was introduced by commit
f8bc271115 ("package/ncftp: bump to
version 3.2.9"). Before it, a pre-configure hook regenerated configure
with autoconf precisely because the bundled script "doesn't detect
cross-compilation correctly". With 3.2.9 that regeneration started to
fail, so the hook was dropped, which brought the broken detection back.
That commit left the host-autoconf dependency behind though, so drop it
now.
The issue is present since 2025.05, and in 2025.02.x since 2025.02.1,
where the 3.2.9 bump was backported as commit
6b0e4d82c3.
Fixes:
https://autobuild.buildroot.org/results/ab25f98d7ab8b397e2aa4f87af9cf1d814f3d6cc/
Fixes: f8bc271115 ("package/ncftp: bump to version 3.2.9")
Assisted-by: Claude:claude-opus-5-5
Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
The bundled CRoaring code enables its x64 specific code paths as soon
as __AVX2__ (or __POPCNT__ and __SSE4_2__) is defined, which also
happens on 32-bit x86 targets such as i686 with BR2_x86_haswell. This
results in calls to 64-bit only intrinsics:
roaring.h:260:18: error: implicit declaration of function '_mm_popcnt_u64'; did you mean '_mm_popcnt_u32'? [-Wimplicit-function-declaration]
Backport the upstream patch that defines DISABLE_X64 when building
for 32-bit x86, so that the portable implementation is used instead.
This issue has been present since commit 0d57555407 ("package/sysprof:
update to version 46.0"), which switched to the new sysprof code base
bundling CRoaring in contrib/eggbitset. It therefore affects 2024.08
and later.
Fixes:
https://autobuild.buildroot.org/results/f00d523aa13923c9eb73ae4e1b1f04f297512351
Fixes: 0d57555407 ("package/sysprof: update to version 46.0")
Assisted-by: Claude:claude-opus-5-5
Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
For change log, see:
https://github.com/sharkdp/hyperfine/blob/v2.0.0/CHANGELOG.md
Changes in v2.0.0 include:
- Add support for alternative performance metrics (peak memory usage,
instructions, CPU cycles, cache misses, branch misses, ...).
- Add --env to set environment variables even without an intermediate
shell.
- Benchmarked commands are now executed directly by default, without
an intermediate shell (--shell=none).
- The JSON format for --export-json has changed (schema version 2).
Refresh the vendored cargo tarball hash for the new release.
Tested using:
utils/test-pkg -c /tmp/hyperfine.config -p hyperfine
(Result: 6 builds, 3 skipped, 0 build failed)
Signed-off-by: Shubham Chakraborty <chakrabortyshubham66@gmail.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Version 2.0.1 fixes an unauthenticated remote denial of service in
version 2.0.0. A single multipart/form-data request containing a file
part without a name attribute can terminate the server process. The
issue is rated high severity with a CVSS 3.1 score of 7.5.
The release also replaces the blocking-start pthread mutex and condition
variable with C++20 atomic wait and notify operations. The existing C++20,
GCC 11 and threads requirements cover this change.
https://github.com/etr/libhttpserver/releases/tag/2.0.1https://github.com/etr/libhttpserver/security/advisories/GHSA-q8g6-h8wv-pr43
Signed-off-by: Stephan Hoffmann <sho@relinux.de>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
uClibc support was disabled in commit:
fb72418160.
This problem is solved in 1.0.59. So in internal
Buildroot toolchains and external Bootlin toolchains.
Tested with aarch64 and external uClibc Bootlin toolchain.
Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
Reviewed-by: Thomas Perale <thomas.perale@mind.be>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
libbpf supports MIPS since commit c86cb27 ("bpf, mips: Fix build errors
about __NR_bpf undeclared", 2021-11-25). Unblock the build by a setting
BR2_PACKAGE_BPFTOOL_ARCH_SUPPORTS=y if a BR2_mips* entry is set.
Built and tested on BR2_mips_64r6.
Signed-off-by: Théo Lebrun <theo.lebrun@bootlin.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
On my system:
$ readelf -d host/sbin/bpftool | awk '/NEEDED/ {$1=""; print}'
(NEEDED) Shared library: [libelf.so.1] # ACK
(NEEDED) Shared library: [libz.so.1] # ACK
(NEEDED) Shared library: [libcap.so.2] # NACK
(NEEDED) Shared library: [libLLVM.so.22.1] # NACK
(NEEDED) Shared library: [libc.so.6] # ACK
After:
$ readelf -d host/sbin/bpftool | awk '/NEEDED/ {$1=""; print}'
(NEEDED) Shared library: [libelf.so.1]
(NEEDED) Shared library: [libz.so.1]
(NEEDED) Shared library: [libc.so.6]
Host bpftool auto-detects optional features by probing the system.
In my case it finds:
- libcap which resolves to my system shared object because
BR2_PACKAGE_LIBCAP=n.
- libLLVM which resolves to the BR2-built one thanks to llvm-config in
$PATH. But we don't have that marked as an explicit dependency.
Avoid the mechanism by hardcoding FEATURE_TESTS to the empty string.
Goal is to make the host-bpftool more hermetic to the host system. If
we ever need those features (future xdp-tools package doesn't), then
we'll add the dependency explicitly.
Signed-off-by: Théo Lebrun <theo.lebrun@bootlin.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
This patch bumps:
- U-Boot to version v2026.10
- Linux kernel to version 6.12.112 (LTS)
Signed-off-by: Dario Binacchi <dario.binacchi@amarulasolutions.com>
[Julien: add link to upstream hash source in linux.hash]
Signed-off-by: Julien Olivain <ju.o@free.fr>
For details see upstream PR 24972 from which these patches were taken
during its development from a force-push which took place May 29, 2024,
8:13 GMT+2.
Please note that the later patches in this PR for ffmpeg 7.1 are not
compatible with Kodi 21.3. We need to use the 7.0 branch of ffmpeg in
order to prepare for the bump of Kodi to 22.0 which supports ffmpeg
versions >= 7.0:
72fe098c84
Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
The servers already redirect from HTTP to HTTPS. Use HTTPS directly to
prevent manipulation along the way.
Also switch from the autobuild.buildroot.net alias to
autobuild.buildroot.org, like all other toolchain downloads from the
Buildroot autobuilder.
Signed-off-by: Fiona Klute <fiona.klute@gmx.de>
Signed-off-by: Julien Olivain <ju.o@free.fr>
Both autobuild.buildroot.org and toolchains.bootlin.com support HTTPS,
and even redirect from HTTP to HTTPS. Use HTTPS directly to prevent
manipulation along the way.
Signed-off-by: Fiona Klute <fiona.klute@gmx.de>
Signed-off-by: Julien Olivain <ju.o@free.fr>
Bump the beagleplay to use the latest stable tfa, uboot and linux kernel
releases to pull in the latest bug fixes and features.
Because swig 4.5.0 removes support for Python 2 compatibility we need to
backport a patch for U-Boot to remove the Python 2 macros it uses to
generate the final fimrware images.
Signed-off-by: Bryan Brattlof <bb@ti.com>
[Julien:
- add "Upstream:" and "Signed-off-by:" tags in patches
- add link to upstream hash source in linux.hash
]
Signed-off-by: Julien Olivain <ju.o@free.fr>
Bump the am64x-sk reference board to use the latest stable tfa, uboot
and linux kernel releases to pull in the latest bug fixes and features.
Because swig 4.5.0 removes support for Python 2 compatibility we need to
backport a patch for U-Boot to remove the Python 2 macros it uses to
generate the final fimrware images.
Signed-off-by: Bryan Brattlof <bb@ti.com>
[Julien:
- add "Upstream:" and "Signed-off-by:" tags in patches
- add link to upstream hash source in linux.hash
]
Signed-off-by: Julien Olivain <ju.o@free.fr>
Bump the am62px-sk reference board to use the latest stable tfa, uboot
and linux kernel releases to pull in the latest bug fixes and features.
Because swig 4.5.0 removes support for Python 2 compatibility we need to
backport a patch for U-Boot to remove the Python 2 macros it uses to
generate the final fimrware images.
Signed-off-by: Bryan Brattlof <bb@ti.com>
[Julien:
- add "Upstream:" and "Signed-off-by:" tags in patches
- add link to upstream hash source in linux.hash
]
Signed-off-by: Julien Olivain <ju.o@free.fr>
Bump the am62ax-sk reference board to use the latest stable tfa, uboot
and linux kernel releases to pull in the latest bug fixes and features.
Because swig 4.5.0 removes support for Python 2 compatibility we need to
backport a patch for U-Boot to remove the Python 2 macros it uses to
generate the final fimrware images.
Signed-off-by: Bryan Brattlof <bb@ti.com>
[Julien:
- add "Upstream:" and "Signed-off-by:" tags in patches
- add link to upstream hash source in linux.hash
]
Signed-off-by: Julien Olivain <ju.o@free.fr>
Select python-typing-extensions, which is now an explicit runtime
dependency.
Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
Signed-off-by: Julien Olivain <ju.o@free.fr>
