Julien Olivain [Thu, 1 Aug 2024 19:50:48 +0000 (21:50 +0200)]
configs/freescale_imx8qxpmek: bump BSP components to lf-6.6.23-2.0.0
Bump ATF, U-Boot and Linux kernel to the NXP BSP lf-6.6.23-2.0.0
versions.
Also, since commit dc0f721 "package/gcc: switch to 13.x as default",
this freescale_imx8qxpmek_defconfig is failing to build the Kernel
with output:
drivers/mxc/gpu-viv/hal/os/linux/kernel/gc_hal_kernel_os.c:5769:1: error: conflicting types for '_QuerySignal' due to enum/integer mismatch; have 'gceSTATUS(struct _gckOS *, void *)' {aka 'enum _gceSTATUS(struct _gckOS *, void *)'} [-Werror=enum-int-mismatch]
5769 | _QuerySignal(
| ^~~~~~~~~~~~
This commit fixes the issue by updating the Kernel.
The BR2_GLOBAL_PATCH_DIR is also changed from
"board/freescale/common/patches" to
"board/freescale/imx8qxpmek/patches". This for two reasons:
1. the common patch directory is removed, because the patches for
arm-trusted-firmware are no longer needed. Patch 0001 is included
in this new version, and patch 0002 no longer needed due a code
rewrite in this new version. The common patch files are kept,
because they are used in other freescale_ defconfigs.
2. the imx8qxpmek patch directory is introduced, to include the needed
hash files, because this commit enables
BR2_DOWNLOAD_FORCE_CHECK_HASHES=y. Those hash files are introduced
in a board specific directory to allow updating this defconfig
independently of the other i.MX defconfigs: there is 16
freescale_imx*_defconfigs, with more or less dependencies
(firmwares, gpu drivers, ...). The ".checkpackageignore" entry for
this defconfig is also removed.
Julien Olivain [Thu, 1 Aug 2024 19:46:49 +0000 (21:46 +0200)]
configs/freescale_imx8qmmek: bump BSP components to lf-6.6.23-2.0.0
Bump ATF, U-Boot and Linux kernel to the NXP BSP lf-6.6.23-2.0.0
versions.
Also, since commit dc0f721 "package/gcc: switch to 13.x as default",
this freescale_imx8qmmek_defconfig is failing to build the Kernel
with output:
drivers/mxc/gpu-viv/hal/os/linux/kernel/gc_hal_kernel_os.c:5769:1: error: conflicting types for '_QuerySignal' due to enum/integer mismatch; have 'gceSTATUS(struct _gckOS *, void *)' {aka 'enum _gceSTATUS(struct _gckOS *, void *)'} [-Werror=enum-int-mismatch]
5769 | _QuerySignal(
| ^~~~~~~~~~~~
This commit fixes the issue by updating the Kernel.
The BR2_GLOBAL_PATCH_DIR is also changed from
"board/freescale/common/patches" to
"board/freescale/imx8qmmek/patches". This for two reasons:
1. the common patch directory is removed, because the patches for
arm-trusted-firmware are no longer needed. Patch 0001 is included
in this new version, and patch 0002 no longer needed due a code
rewrite in this new version. The common patch files are kept,
because they are used in other freescale_ defconfigs.
2. the imx8qmmek patch directory is introduced, to include the needed
hash files, because this commit enables
BR2_DOWNLOAD_FORCE_CHECK_HASHES=y. Those hash files are introduced
in a board specific directory to allow updating this defconfig
independently of the other i.MX defconfigs: there is 16
freescale_imx*_defconfigs, with more or less dependencies
(firmwares, gpu drivers, ...). The ".checkpackageignore" entry for
this defconfig is also removed.
Julien Olivain [Thu, 1 Aug 2024 19:15:05 +0000 (21:15 +0200)]
package/freescale-imx/firmware-imx: bump version to 8.24
This version is aligned with NXP Linux BSP version "lf-6.6.23-2.0.0".
License hashes changed because the LA_OPT_NXP_Software_License changed
from "v49 September 2023" to "v56 April 2024".
Note: in this release, the package source archive name changed to
include a revision. This commit adds a new _REVISION variable with the
value published in the corresponding NXP BSP. See [1].
Julien Olivain [Thu, 1 Aug 2024 17:49:54 +0000 (19:49 +0200)]
configs/freescale_imx8mnevk: bump BSP components to lf-6.6.23-2.0.0
Bump ATF, U-Boot and Linux kernel to the NXP BSP lf-6.6.23-2.0.0
versions.
Also, since commit dc0f721 "package/gcc: switch to 13.x as default",
this freescale_imx8mnevk_defconfig is failing to build the Kernel
with output:
drivers/mxc/gpu-viv/hal/os/linux/kernel/gc_hal_kernel_os.c:5769:1: error: conflicting types for '_QuerySignal' due to enum/integer mismatch; have 'gceSTATUS(struct _gckOS *, void *)' {aka 'enum _gceSTATUS(struct _gckOS *, void *)'} [-Werror=enum-int-mismatch]
5769 | _QuerySignal(
| ^~~~~~~~~~~~
This commit fixes the issue by updating the Kernel.
The BR2_GLOBAL_PATCH_DIR is also changed from
"board/freescale/common/patches" to
"board/freescale/imx8mnevk/patches". This for two reasons:
1. the common patch directory is removed, because the patches for
arm-trusted-firmware are no longer needed. Patch 0001 is included
in this new version, and patch 0002 no longer needed due a code
rewrite in this new version. The common patch files are kept,
because they are used in other freescale_ defconfigs.
2. the imx8mnevk patch directory is introduced, to include the needed
hash files, because this commit enables
BR2_DOWNLOAD_FORCE_CHECK_HASHES=y. Those hash files are introduced
in a board specific directory to allow updating this defconfig
independently of the other i.MX defconfigs: there is 16
freescale_imx*_defconfigs, with more or less dependencies
(firmwares, gpu drivers, ...). The ".checkpackageignore" entry for
this defconfig is also removed.
Julien Olivain [Thu, 1 Aug 2024 17:44:53 +0000 (19:44 +0200)]
configs/freescale_imx8mpevk: bump BSP components to lf-6.6.23-2.0.0
Bump ATF, U-Boot and Linux kernel to the NXP BSP lf-6.6.23-2.0.0
versions.
Also, since commit dc0f721 "package/gcc: switch to 13.x as default",
this freescale_imx8mpevk_defconfig is failing to build the Kernel
with output:
drivers/mxc/gpu-viv/hal/os/linux/kernel/gc_hal_kernel_os.c:5675:1: error: conflicting types for '_QuerySignal' due to enum/integer mismatch; have 'gceSTATUS(struct _gckOS *, void *)' {aka 'enum _gceSTATUS(struct _gckOS *, void *)'} [-Werror=enum-int-mismatch]
5675 | _QuerySignal(IN gckOS Os, IN gctSIGNAL Signal)
| ^~~~~~~~~~~~
This commit fixes the issue by updating the Kernel.
This commit also adds the custom version package hashes. Therefore,
BR2_DOWNLOAD_FORCE_CHECK_HASHES=y is added in the defconfig, a
BR2_GLOBAL_PATCH_DIR is also added in the board specific directory and
the hash files are added.
In file included from <command-line>:
drivers/ata/libahci.c: In function 'ahci_led_store':
././include/linux/compiler_types.h:322:45: error: call to '__compiletime_assert_329' declared with attribute error: BUILD_BUG_ON failed: sizeof(_s) > sizeof(long)
This commit fixes this by using the opportunity to bump the kernel to
the latest LTS version. While bumping the kernel, the headers to use
are also updated, and the selected device trees are updated to use the
new dts per vendor organization.
This update does not introduce any new error or warning with the
current configuration.
See release announce:
https://www.freerdp.com/2024/04/22/2_11_7-release
Note: this release is flagged as a "security" bump from the upstream
release note. While there is no allocated CVEs, commits in this release
are backported fixes from oss-fuzz. See:
https://github.com/FreeRDP/FreeRDP/compare/2.11.6...2.11.7
configs/beaglebone_defconfig: add hashes for Linux/headers/U-Boot
The patch adds .hash files for Linux, Linux headers and U-Boot and then
enables BR2_DOWNLOAD_FORCE_CHECK_HASHES. With this, we can now drop the
defconfig from .checkpackageignore.
configs/beaglebone_qt5: move patches to beaglebone-qt5 folder
Compared to the beaglebone_defconfig, updating the Linux kernel for
beaglebone_qt5 is more tricky because it may also involve updating the
ti-sgx-{km,um} packages. Therefore, it is unlikely that the two
configurations can share the same software versions for the Linux
kernel, and consequently a single path for the patches. For this
reason, and with the foresight of adding the hash files for the
beaglebone_defconfig as well, the hash files and patches are moved to
a separate board/beagleboard/beaglebone-qt5/patches/ directory. This
way, future conflicts in managing the patches for the two
configurations (i.e., beaglebone[_qt5]_defconfig) are avoided.
Commit e2520d0ff3d8e ("configs/beaglebone_qt5: bump kernel and U-Boot,
add weston") selected host-uboot-tools with FIT support to create the
images. They are no longer necessary now.
Thomas Petazzoni [Fri, 19 Jul 2024 21:03:24 +0000 (23:03 +0200)]
package/gcc: fix build with BR2_TIME_BITS_64=y
On the architectures that supports libsanitizer (part of gcc), the
build is currently failing with BR2_TIME_BITS_64=y. This is because
some code in libsanitizer unsets _FILE_OFFSET_BITS, but building code
with _FILE_OFFSET_BITS unset, but _TIME_BITS set isn't legal.
To fix this, this commit backports two changes:
- One change to also unset _TIME_BITS in
sanitizer_platform_limits_posix.cpp. This change is upstream in
LLVM, and already part of GCC 14.x, so we only bringing it to GCC
12.x and GCC 13.x.
- A second change doing the same modification, but in
sanitizer_procmaps_solaris.cpp, which as crazy as it might sound,
also gets compiled on Linux platforms (but to basically an empty
file). This change has been submitted upstream to both LLVM and gcc.
Notes:
- the special PowerPC SPE version of GCC cannot be affected, as only
uClibc-ng is used for this architecture, and uClibc-ng doesn't use
_TIME_BITS=64 (but now default to 64-bit time_t on 32-bit
architectures, like musl does).
- the special ARC version doesn't need patching because libsanitizer
doesn't support the ARC architecture, so it doesn't get built
Thomas Petazzoni [Fri, 19 Jul 2024 20:58:01 +0000 (22:58 +0200)]
arch/Config.in.x86: drop knightslanding and knightsmill archs
According to the GCC 14.x release notes at
https://gcc.gnu.org/gcc-14/changes.html:
Xeon Phi CPUs support (a.k.a. Knight Landing and Knight Mill) are
marked as deprecated. GCC will emit a warning when using the
-mavx5124fmaps, -mavx5124vnniw, -mavx512er, -mavx512pf,
-mprefetchwt1, -march=knl, -march=knm, -mtune=knl or -mtune=knm
compiler switches. Support will be removed in GCC 15.
Using those architectures already emits warnings, which when treated
as errors cause build failures, such as:
cc1: error: '-march=knm' support will be removed in GCC 15 [-Werror=deprecated]
cc1: all warnings being treated as errors
Therefore, let's drop support for those two architectures, which are
anyway not common at all, especially in the embedded space.
In file included from ../src/dex-uring-aio-backend.c:29:
/home/autobuild/autobuild/instance-7/output-1/host/mips-buildroot-linux-musl/sysroot/usr/include/liburing.h:224:39: error: unknown type name 'cpu_set_t'
224 | const cpu_set_t *mask);
| ^~~~~~~~~
/home/autobuild/autobuild/instance-7/output-1/host/mips-buildroot-linux-musl/sysroot/usr/include/liburing.h:1212:48: error: unknown type name 'loff_t'; did you mean 'off_t'?
1212 | int fd, loff_t len)
| ^~~~~~
| off_t
Following Microchip's Linux 2024.06 release, bump Linux and U-Boot to
the most recent versions. Also update the Linux custom headers to
support the new v6.6 kernel. Update all affected hashes.
configs/microchip_mpfs_icicle: bump Linux and U-Boot, add hashes
Following Microchip's Linux 2024.06 release, update the assets to the
latest versions, this includes a Linux and U-boot version bump. Update
the Linux headers to support the updated v6.6 kernel.
This defconfig was added before the "BR2_DOWNLOAD_FORCE_CHECK_HASHES"
option was mandatory. Add this and the corresponding package hashes.
arm-aarch64 [ 1/41]: OK
bootlin-aarch64-glibc [ 2/41]: OK
bootlin-arcle-hs38-uclibc [ 3/41]: OK
bootlin-armv5-uclibc [ 4/41]: OK
bootlin-armv7-glibc [ 5/41]: OK
bootlin-armv7m-uclibc [ 6/41]: SKIPPED
bootlin-armv7-musl [ 7/41]: OK
bootlin-m68k-5208-uclibc [ 8/41]: SKIPPED
bootlin-m68k-68040-uclibc [ 9/41]: OK
bootlin-microblazeel-uclibc [10/41]: OK
bootlin-mipsel32r6-glibc [11/41]: OK
bootlin-mipsel-uclibc [12/41]: OK
bootlin-nios2-glibc [13/41]: OK
bootlin-openrisc-uclibc [14/41]: OK
bootlin-powerpc64le-power8-glibc [15/41]: OK
bootlin-powerpc-e500mc-uclibc [16/41]: OK
bootlin-riscv32-glibc [17/41]: OK
bootlin-riscv64-glibc [18/41]: OK
bootlin-riscv64-musl [19/41]: OK
bootlin-s390x-z13-glibc [20/41]: OK
bootlin-sh4-uclibc [21/41]: OK
bootlin-sparc64-glibc [22/41]: OK
bootlin-sparc-uclibc [23/41]: OK
bootlin-x86-64-glibc [24/41]: OK
bootlin-x86-64-musl [25/41]: OK
bootlin-x86-64-uclibc [26/41]: OK
bootlin-x86-i686-musl [27/41]: OK
bootlin-xtensa-uclibc [28/41]: OK
br-arm-basic [29/41]: OK
br-arm-full-nothread [30/41]: OK
br-arm-full-static [31/41]: OK
br-i386-pentium4-full [32/41]: OK
br-mips64-n64-full [33/41]: OK
br-mips64r6-el-hf-glibc [34/41]: OK
br-powerpc-603e-basic-cpp [35/41]: OK
br-powerpc64-power7-glibc [36/41]: OK
linaro-aarch64-be [37/41]: OK
linaro-aarch64 [38/41]: OK
linaro-arm [39/41]: OK
sourcery-mips64 [40/41]: OK
sourcery-mips [41/41]: OK
41 builds, 2 skipped, 0 build failed, 0 legal-info failed, 0 show-info failed
BR2_PACKAGE_GNUTLS=y
BR2_PACKAGE_OPENCONNECT=y
arm-aarch64 [ 1/41]: OK
bootlin-aarch64-glibc [ 2/41]: OK
bootlin-arcle-hs38-uclibc [ 3/41]: OK
bootlin-armv5-uclibc [ 4/41]: OK
bootlin-armv7-glibc [ 5/41]: OK
bootlin-armv7m-uclibc [ 6/41]: SKIPPED
bootlin-armv7-musl [ 7/41]: OK
bootlin-m68k-5208-uclibc [ 8/41]: SKIPPED
bootlin-m68k-68040-uclibc [ 9/41]: OK
bootlin-microblazeel-uclibc [10/41]: OK
bootlin-mipsel32r6-glibc [11/41]: OK
bootlin-mipsel-uclibc [12/41]: OK
bootlin-nios2-glibc [13/41]: OK
bootlin-openrisc-uclibc [14/41]: OK
bootlin-powerpc64le-power8-glibc [15/41]: OK
bootlin-powerpc-e500mc-uclibc [16/41]: OK
bootlin-riscv32-glibc [17/41]: OK
bootlin-riscv64-glibc [18/41]: OK
bootlin-riscv64-musl [19/41]: OK
bootlin-s390x-z13-glibc [20/41]: OK
bootlin-sh4-uclibc [21/41]: OK
bootlin-sparc64-glibc [22/41]: OK
bootlin-sparc-uclibc [23/41]: OK
bootlin-x86-64-glibc [24/41]: OK
bootlin-x86-64-musl [25/41]: OK
bootlin-x86-64-uclibc [26/41]: OK
bootlin-x86-i686-musl [27/41]: OK
bootlin-xtensa-uclibc [28/41]: OK
br-arm-basic [29/41]: SKIPPED
br-arm-full-nothread [30/41]: OK
br-arm-full-static [31/41]: SKIPPED
br-i386-pentium4-full [32/41]: OK
br-mips64-n64-full [33/41]: OK
br-mips64r6-el-hf-glibc [34/41]: OK
br-powerpc-603e-basic-cpp [35/41]: SKIPPED
br-powerpc64-power7-glibc [36/41]: OK
linaro-aarch64-be [37/41]: OK
linaro-aarch64 [38/41]: OK
linaro-arm [39/41]: OK
sourcery-mips64 [40/41]: OK
sourcery-mips [41/41]: OK
Last release dates back to 2016, project is active so bump to current
HEAD. Upstream issue to tag a new release is open:
https://github.com/Tencent/rapidjson/issues/2284
configs/freescale_imx7dsabresd: bump BSP components to lf-6.6.23-2.0.0
This commit bumps U-Boot and Linux kernel to the NXP BSP
lf-6.6.23-2.0.0 versions.
While bumping those BSP components, this commit also adds the custom
hashes by enabling BR2_DOWNLOAD_FORCE_CHECK_HASHES=y in this
defconfig. A _PATCH_DIR is added for that purpose and hash files are
added in it. The ".checkpackageignore" entry for this defconfig is
also removed.
Also, since commit dc0f721 "package/gcc: switch to 13.x as default",
this freescale_imx7dsabresd_defconfig is failing to build the Kernel
with output:
drivers/ata/libahci.c: In function 'ahci_led_store':
././include/linux/compiler_types.h:315:45: error: call to '__compiletime_assert_340' declared with attribute error: BUILD_BUG_ON failed: sizeof(_s) > sizeof(long)
315 | _compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__)
| ^
This commit fixes the issue by bumping components which includes the
needed gcc-13 fixes.
The Kernel DTS name is also updated by adding the new "nxp/imx/"
prefix, to follow the upstream reorganization in [1], first included
in v6.5.
configs/freescale_imx6{dl, q, sx}*: bump BSP components to lf-6.6.23-2.0.0
Note: configs/freescale_imx6{dl,q,sx}* corresponds to the five:
freescale_imx6dlsabreauto_defconfig
freescale_imx6dlsabresd_defconfig
freescale_imx6qsabreauto_defconfig
freescale_imx6qsabresd_defconfig
freescale_imx6sxsabresd_defconfig
Those i.MX6 Sabre defconfigs have a lot in common. This is why they are
all updated at once in this single commit.
This commit bumps U-Boot and Linux kernel to the NXP BSP
lf-6.6.23-2.0.0 versions. The imx6sabre uboot patch is also rebased on
the new version, and the "Upstream:" tag is added to flag this patch
as Buildroot-specific. The ".checkpackageignore" entry for this patch
is also removed.
While bumping those BSP components, this commit also adds the custom
hashes by enabling BR2_DOWNLOAD_FORCE_CHECK_HASHES=y in those
defconfigs. Hash files are added in the _PATCH_DIR. The
".checkpackageignore" entries for those defconfigs are also removed.
Also, since commit dc0f721 "package/gcc: switch to 13.x as default",
those freescale_imx6{dl,q,sx}* are failing to build the Kernel
with output:
drivers/ata/libahci.c: In function 'ahci_led_store':
././include/linux/compiler_types.h:315:45: error: call to '__compiletime_assert_340' declared with attribute error: BUILD_BUG_ON failed: sizeof(_s) > sizeof(long)
315 | _compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__)
| ^
This commit fixes the issue by bumping components which includes the
needed gcc-13 fixes.
The Kernel DTS names are also updated by adding the new "nxp/imx/"
prefix, to follow the upstream reorganization in [1], first included
in v6.5.
boot/xilinx-prebuilt: support future AMD Vivado versions
When creating a hardware platform for AMD Versal devices with the AMD Vivado
Design Suite, the resulting XSA file has a file named "psm_fw.elf" included.
This does not match the "psmfw.elf" filename that users will get when building
the boot firmware from the Xilinx GIT repository.
A change request has been submitted to resolve this issue, so that future
AMD Vivado Design Suite versions will generate XSA files including the boot
firmware file named "psmfw.elf" to match the filename that is generated when
building the firmware.
In order to support both current and future versions of AMD Vivado Design
Suite, this patch changes the xilinx-prebuilt package to use the filename
"psm*fw.elf" when obtaining the Versal boot firmware images from a user
generated XSA file.
Joachim Wiberg [Mon, 29 Jul 2024 06:34:20 +0000 (08:34 +0200)]
package/sysklogd: bump to v2.6.1
From https://github.com/troglobit/sysklogd/releases/tag/v2.6.1:
- Read .conf files from include directories sorted alphabetically
- Add extra linefeed to wall messages to ensure they are seen
- Fix segfault on SIGTERM, regression from v2.6.0
In file included from BitStream.C:23:
../include/BitStream.H:35:2: error: #error "iobitstream not tested on big endian systems"
35 | #error "iobitstream not tested on big endian systems"
| ^~~~~
support/testing/infra/emulator.py: add host load info in run log
Runtime tests running on test runners are subject to a high
variability in term of performance and timing. Most or the runtime
test commands are executed with a timeout, in pexpect.
Slow or very loaded test runners can use the timeout_multiplier to
globally increase those timeouts.
Some runtime test commands sometimes needs to poll or query a state,
rather than having purely sequential actions. It is sometimes hard to
know, from the test writer point of view, the maximum timeout to set, or
if a retry logic is needed.
In order to help debugging runtime tests failing due very slow
execution, this commit adds extra information on the host test runner
about its load in the run log. Relevant information are: number of
cpus, the load average at the moment the emulator is started and the
current timeout_multiplier.
Note: this change was discussed in:
https://lists.buildroot.org/pipermail/buildroot/2024-July/759119.html
Thomas Petazzoni [Sun, 28 Jul 2024 16:34:10 +0000 (18:34 +0200)]
package/gdb: move GDB 14.x patches to the right folder
Commit bfefed17a9e5a421b3217685003d3b22c99de4ab ("package/gdb: bump
14.x series from 14.1 to 14.2"), which upgraded the GDB 14.x series
from 14.1 to 14.2 forgot to rename the directory containing the
patches, causing them to no longer be applied.
The patches still apply properly with no change, so renaming the
directory is sufficient.
GCC 14 errors out on the implicit return type of "main() {}". The
patch also removes the /dev/null redirection of GCC stderr that hid
the actual problem.
J. Neuschäfer [Fri, 26 Jul 2024 20:03:52 +0000 (22:03 +0200)]
support/testing: fix s6-portable-utils test
s6-test was removed in s6-portable-utils 2.3.0.0, and replaced with
eltest (from execline). This change broke the existing runtime tests
with commit 42fad03182 ("packages: bump skalibs-related packages").
Instead of s6-test simply use the shell built-in "test", which provides
sufficient functionality.
softhsm2 unconditionally calls the (deprecated) ENGINE_* logic in
libopenssl resulting in a build failure when
!BR2_PACKAGE_LIBOPENSSL_ENGINES since commit 623d3bbe43e9193aa8e3395367d01af59071b859:
OSSLCryptoFactory.cpp: In constructor 'OSSLCryptoFactory::OSSLCryptoFactory()':
OSSLCryptoFactory.cpp:146:9: error: 'ENGINE_load_rdrand' was not declared in this scope
146 | ENGINE_load_rdrand();
| ^~~~~~~~~~~~~~~~~~
The libpwquality package provides the pam_pwquality PAM module - the
replacement for pam_cracklib that was dropped from linux-pam back in
version 1.5.0. However, it currently installs it to the wrong place,
so passwd and friends fail to find it. This commit sets the security
directory path to /lib/security to match the corresponding setting in
linux-pam.mk.
Note that libpwquality has *always* installed pam_pwquality in the wrong
place, since version 1.3.0 was added to buildroot in 2017 in commit 462040443ca943694fc59ec8380c82f8bf9aaddc. However, back then, linux-pam
version 1.3.0 still provided pam_cracklib for advanced password checking.
Linux-pam deprecated pam_cracklib in 1.4.0 but still built it for us when
linux-pam.mk set --enable-cracklib. Linux-PAM deleted pam_cracklib
altogether in 1.5.0, so it was not until our update to linux-pam-1.5.1
in commit 276f1e0a896698abec85500a86686bf72c79eb91 that pam_cracklib
became unavailable. After that point, pam_pwquality was the only
alternative for PAM-based password checking.
dwelf_elf_begin.c:62:1: error: symver is only supported on ELF platforms
62 | OLD_VERSION (dwelf_elf_begin, ELFUTILS_0.175)
| ^~~~~~~~~~~
dwelf_elf_begin.c:62:1: error: symver is only supported on ELF platforms
Developers may have multiple output directories when building multiple
boards in parallel. A previous commit attempted to gitignore new output
directories automatically but broke some things (commit a14c862c08
"Create a .gitignore file in the CANONICAL_O directory").
To provide some support, ignore anything in the Buildroot directory that
starts with "output". This is a bit more cumbersome, but doesn't break
packages based on Python maturin.
Revert "Create a .gitignore file in the CANONICAL_O directory"
The packages 'python-jsonschema-specifications', 'pydantic-core', and
likely other packages based on Python maturin silently stopped
installing files to the host and target directories after commit a14c862c08.
A similar issue was reported by the Conda project[1]. It seems some
build tools scan for gitignore files to decide what files to build
and install.
I attempted various combinations of gitignore patterns including
mimicking the Conda project's gitignore[2], but the only thing that has
worked reliably is the original `/output` ignore in the root Buildroot
directory.
When using BR2_STATIC_LIBS=y, tinysshd's build was successful, but the
binary didn't work on the final target: this is because a dynamically
linked ELF was produced, on a target having no dynamic loader at all.
Using $(TARGET_CONFIGURE_OPTS) propagates all the options and not only
"CC", resulting in a correct static binary able to run on the target.
package/lrzsz: drop unused LRZSZ_POST_CONFIGURE_HOOKS
As already done for LRZSZ_BUILD_HOOKS in commit 5fde4abc8d67ac2317b1de7a1b4cde8091f4e3c7, drop bogus
LRZSZ_POST_CONFIGURE_HOOKS as this hook added in 2010 is also never
called
/usr/bin/install -m 644 -D -T /home/buildroot/autobuild/instance-3/output-1/build/wireless-regdb-2024.07.04/sforshee.key.pub.pem /home/buildroot/autobuild/instance-3/output-1/target/etc/wireless-regdb/pubkeys/sforshee.key.pub.pem
/usr/bin/install: cannot stat '/home/buildroot/autobuild/instance-3/output-1/build/wireless-regdb-2024.07.04/sforshee.key.pub.pem': No such file or directory
j1939acd.c: In function 'main':
j1939acd.c:489:38: error: passing argument 1 of 'asprintf' from incompatible pointer type [-Wincompatible-pointer-types]
489 | if (asprintf(&program_invocation_name, "%s.%s",
| ^~~~~~~~~~~~~~~~~~~~~~~~
| |
| const char **
In file included from /home/autobuild/autobuild/instance-23/output-1/build/libressl-3.8.4/crypto/rc4/rc4_enc.c:61:
/home/autobuild/autobuild/instance-23/output-1/build/libressl-3.8.4/crypto/../include/openssl/rc4.h:75:9: error: unknown type name 'RC4_INT'
75 | RC4_INT x, y;
| ^~~~~~~
- Switch site to get latest release
- Send patch upstream
- This bump will fix the following build failure with gcc >= 14:
src/main.c: In function 'main':
src/main.c:211:17: error: implicit declaration of function 'quota_reset_grace'; did you mean 'xfs_reset_grace'? [-Wimplicit-function-declaration]
211 | if (! quota_reset_grace(quota, (argdata->block_reset ? GRACE_BLOCK : GRACE_INODE)))
| ^~~~~~~~~~~~~~~~~
| xfs_reset_grace
- Drop all patches (already in version) and so also drop autoreconf
- This bump will also fix the following build failure with gcc >= 14:
pgrep.c: In function 'main':
pgrep.c:1066:37: error: implicit declaration of function 'pidfd_open'; did you mean 'fdopen'? [-Wimplicit-function-declaration]
1066 | int pidfd = pidfd_open(procs[i].num, 0);
| ^~~~~~~~~~
| fdopen
projects / buildroot-mgba.git / log