Like Yann E. Morin did for
support/testing/tests/package/test_python_django.py, adjust the logic
to avoid the weird "self.assertTrue(False, ...)" construct, and
instead test exit_code after the loop.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
The test runs the flask sample app through the waitress wsgi server
instead of the flask development server.
Signed-off-by: Marcus Hoffmann <buildroot@bubu1.eu>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Migrate protobuf build from autotools to cmake.
Migrate protobuf-python to use pypi sources which are now required
for setup.py builds:
https://github.com/protocolbuffers/protobuf/tree/v28.1/python#building-from-setuppy
The BR2_or1k workaround is removed, as protobuf depends on
libabseil-cpp, which isn't available on OpenRISC.
The BR2_TOOLCHAIN_HAS_GCC_BUG_85180 workaround is removed, as this
workaround is for Microblaze, and protobuf depends on libabseil-cpp,
which isn't avialable on Microblaze.
Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
[Arnout: remove netbird whch was accidentally added]
Signed-off-by: Arnout Vandecappelle <arnout@mind.be>
We need to use the latest git commit as the last release does not
support compiling with the newer protobuf releases.
Add optional mosquito support.
Add librtlsdr mosquito support.
Fix python-setuptools dependency which should be
host-python-setuptools.
Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
Signed-off-by: Arnout Vandecappelle <arnout@mind.be>
Commit [1] introduced the BR2_BROKEN hidden symbol. The intent of
this symbol is to temporarily mark a configuration known to be broken.
This commit was added to fix an undefined usage of the symbol, in a
previous commit [2].
With this somewhat special symbol, it is also perfectly normal to
have no use of it.
Running the command "utils/check-symbols" in a state there is no usage
of the BR2_BROKEN, the script fails with output:
Config.in:15: BR2_BROKEN defined but not referenced
This commit adds an exception for this symbol, allowing it to be
unused in the whole Buildroot tree.
Fixes:
https://gitlab.com/buildroot.org/buildroot/-/jobs/8925433382
[1] 2ddc5808cd
[2] 11a8cdd2bb
Signed-off-by: Julien Olivain <ju.o@free.fr>
Signed-off-by: Romain Naour <romain.naour@smile.fr>
This allows using simple displays not directly connected to the GPU,
and platforms supported only via Vulkan.
Signed-off-by: Fiona Klute (WIWA) <fiona.klute@gmx.de>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Commit 6ecab31fad bumped glibc to
version 2.41, but forgot to update the associated legal information.
Indeed, the LICENSES file has changed upstream, with a few commits
between 2.40 and 2.41:
- 2843e78b30da0aa743fdfb0ac61435c925182c04
Adds another MIT license. We already list MIT in the licenses
- d421d36582281a62e05f96a1bfb085db9d85f40b
Adds URL of a project included in glibc. No license change.
- 4871ab841b3bfbabdba62cc86dd6b8db84f5c134
Drops Intel License Agreement due to IA64 removal, which was in fact
BSD-3-Clause, but there's still BSD-3-Clause code in glibc, and this
license is therefore still listed in GLIBC_LICENSE as it should be
- 1ed3e4468879b79492dfd453255b9318b3265843
Updates some file locations. No license change.
- aba14403c606fdba6726f76442272d5011c52900
Updates CORE-MATH copyright. No license change.
Fixes:
http://autobuild.buildroot.net/results/74fb3ade56140cf8c0496f1d087f0b33ee6b6ff3/
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
The k3-am62a7-sk.dts describes an I2C PMIC TPS659312 which features a
number of regulators. One of them, ldo1, is used as power supply for the
SD card host controller regulator. When the rootfs is on the SD
card (like with this configuration), we need support for these three
components (Regulator driver, I2C PMIC glue and PMIC MFD driver) to be
built-in in order to avoid boot failures.
Tested on an AM62A LP SK.
Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
Reviewed-by: Bryan Brattlof <bb@ti.com>
Signed-off-by: Romain Naour <romain.naour@smile.fr>
Commit 360fd01de2 changed the binutils
package to use 2.43.x as the default version, but got the change wrong
in the BINUTILS_VERSION variable assignment. Indeed we don't support
2.43, but 2.43.1. This issue is causing the following build failure:
ERROR: No hash found for binutils-2.43.tar.xz
Fixes:
https://gitlab.com/vjardin/buildroot/-/jobs/9043815781
Signed-off-by: Vincent Jardin <vjardin@free.fr>
[Thomas: proper fix, and improved commit log]
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Aiomqtt uses Poetry. The only difference between poetry and generic
pep517 is the host-python-poetry-core dependency, and this got pulled in
as an indirect dependency of host-python-poetry-dynamic-versioning so
far. So the build was not actually failing, but it's better to be
correct.
Signed-off-by: Fiona Klute (WIWA) <fiona.klute@gmx.de>
Signed-off-by: Arnout Vandecappelle <arnout@mind.be>
For the `b4` tool to support check-package, check-package must support
reading patch files from stdin.
It would be complicated to make check-package actually run checks on
patch files. So instead we search the patch files to figure out what
files are modified in the repo, then run check-package on the modified
files directly.
Signed-off-by: Brandon Maier <brandon.maier@collins.com>
[Arnout: rename variable "files" to "files_to_check"]
Signed-off-by: Arnout Vandecappelle <arnout@mind.be>
This package provides firmwares for NXP WiFi + Bluetooth chipsets.
It is named "nxp-bt-wifi-firmware" so that it is not confused with the
package firmware-imx.
Signed-off-by: Sébastien Szymanski <sebastien.szymanski@armadeus.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
The patch bumps the Linux kernel to version 6.1.126. The size of xipImage
has increased by only 284 bytes (1670242 bytes compared to 1670242 in
version 6.1.112).
Signed-off-by: Dario Binacchi <dario.binacchi@amarulasolutions.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
The patch bumps the Linux kernel to version 5.15.176 and, for the SD
configuration, also updates U-Boot to version 2025.01.
Signed-off-by: Dario Binacchi <dario.binacchi@amarulasolutions.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
This is the latest version available in Debian (which is our upstream
for this package). The changelog is:
[ Ben Hutchings ]
* Fix FTBFS with gcc 11 (Closes: #1005413):
- Remove exception specifications
* Fix module build for recent kernel versions (Closes: #1005414):
- Stop generating module vermagic in cloop.c. This has always been handled
by modpost and doing it here now results in build failure.
- Avoid using inode::i_bdev, which was removed in Linux 5.11.
- Use set_disk_ro() instead of set_device_ro(). The latter was not meant to
be used by device drivers and was removed in Linux 5.11.
- Use blk_{mq_alloc,cleanup}_disk() instead of separate queue and disk
allocation and cleanup on Linux 5.15+, since alloc_disk() was removed.
- Handle potential failure of add_disk() on Linux 5.15+.
- Use kernel_read() instead of vfs_read() and set_fs(). set_fs() is no
longer defined on some architectures, and kernel_read() has had large
file support since Linux 2.6.31.
.
[ Vagrant Cascadian ]
* debian/rules: Build tarball reproducibly, using consistent time, uid,
gid and sort order. Thanks to Dhole for the initial patch.
The "Fix FTBFS with gcc 11" allows us to remove the -std=c++14
workaround added in commit
7e147e778f ("package/cloop: fix build
with gcc >= 9").
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
[Arnout: use debian snapshot instead of debian-debug]
Signed-off-by: Arnout Vandecappelle <arnout@mind.be>
Current gobject-introspection releases (>= 1.80.1) work with musl, so
relax the C library requirement for python-gobject to match.
Signed-off-by: Fiona Klute (WIWA) <fiona.klute@gmx.de>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Current versions of gobject-introspection build with musl (Alpine
dropped the last compatibility patch with the update to 1.80.1 [0]), so
relax the dependency on glibc.
[0] 528c4ee639
Signed-off-by: Fiona Klute (WIWA) <fiona.klute@gmx.de>
[yann.morin.1998@free.fr: split off to its own patch]
Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
There are a lot of interconnected changes in these releases:
Since 2.79.0, the introspection (i11n) data for libglib2 was moved out
of gobject-introspection (GOI) and into libglib2 itself, thus building
libglib2 with i11n needs tools provided by GOI [0].
However, GOI needs libglib2, but it is content with a libglib2 that
does not have i11n. So we introduce a new package, libglib2-bootstrap,
that provides a minimalist libglib2 that is enough to build GOI, build
GOI, then build the final, complete libglib2 with i11n.
However, not every package needs i11n, so we make that optional: if GOI
is enabled, libglib2 will have i11n, otherwise it won't.
This means the dependency ordering has changed: GOI used to
build-depend on libglib2, but now that's the other way around. This
will cause issues with packages that build-depend only on GOI and then
expect a libglib2 with i11n; those will only get a basic libglib2
without i11n at build time, but a full one at runtime. Those packages
will have to be fixed to also include a build dependency on libglib2.
The version bump between libglib2 and GOI must be done in lock-step,
because newer GOI does not support an older libglib2 and, as seen
above, newer libglib2 has the data previously provided by older GOI.
As a consequence of now generating its own i11n data, libglib2 needs to
be able to run target programs during the build, to extract data layout
and generate i11n data, a bit like GOI does [1]. So we provide a qemu
wrapper similar to the one in nodejs-src, and use that as meson's
exe_wrapper.
Except for our first patch, the other libglib2 patches were backports,
and are present upstream already, so we can drop them; the first patch
needs being refreshed.
We also move the remaining patch to a versioned sub-directory, so that
it is easier to share the patches between libglib2-bootstrap and
libglib2, should we need to add more patches in the future.
Drop the "giscanner: remove dependency on distutils.msvccompile"
patch, included upstream.
Updated hash for giscanner/scannerlexer.l is due to code changes, no
change in license, see [2] (two commits in 2024).
[0] https://gitlab.gnome.org/GNOME/glib/-/blob/2.79.0/NEWS?ref_type=tags#L8-17
[1] technically, this should not be needed if libglib2 only uses the
wrappers provided by GOI: g-ir-scanner et al. However, its
meson.build explicitly checks that it can run generated binaries
through the exe_wrapper. Investigating if that's really needed is
left as an exercise for the interested party: in practice, we will
have to be able to run via host-qemu, so this does not add any build
time overhead.
[2] https://gitlab.gnome.org/GNOME/gobject-introspection/-/commits/1.82.0/giscanner/scannerlexer.l?ref_type=tags
Signed-off-by: Fiona Klute (WIWA) <fiona.klute@gmx.de>
Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
Tested-by: Marcus Hoffmann <buildroot@bubu1.eu>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Required to build with gobject-introspection >= 1.82.0, to be bumped
in a later commit.
License information has been restructured according to REUSE
guidelines, see [1]. Update hashes and license information
accordingly.
[1] a06d43db36
Signed-off-by: Fiona Klute (WIWA) <fiona.klute@gmx.de>
Tested-by: Marcus Hoffmann <buildroot@bubu1.eu>
[Thomas: do not list .reuse/dep5 in license files]
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Since the bump of NetworkManager to 1.50.0 in Buildroot commit
489d1f9249, the
tests.package.test_python_sdbus_networkmanager.TestPythonPy3SdbusNetworkmanager
is failing to build as NM >= 1.50.0 needs headers >= 4.20.
We fix this test by using a newer toolchain. This means we can't use
anymore the basic toolchain config, so we use a fully specific
defconfig for this test.
Fixes:
https://gitlab.com/buildroot.org/buildroot/-/jobs/9019173666
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Since the bump of NetworkManager to version 1.50 in Buildroot commit
489d1f9249, it uses the
NETLINK_GET_STRICT_CHK netlink macro, which only appeared in Linux
4.20, so let's add a dependency on headers >= 4.20.
This has been detected by our
tests.package.test_python_sdbus_networkmanager.TestPythonPy3SdbusNetworkmanager
at:
https://gitlab.com/buildroot.org/buildroot/-/jobs/9019173666
NetworkManager is not selected by any package, so only fixing
package/network-manager/Config.in is necessary.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
