This repository has been archived by the owner on Jun 28, 2021. It is now read-only.
Update buildroot fork to latest upstream master #8
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
Signed-off-by: James Hilliard <[email protected]> Signed-off-by: Thomas Petazzoni <[email protected]>
Signed-off-by: James Hilliard <[email protected]> Signed-off-by: Thomas Petazzoni <[email protected]>
Currently, goi depends on cairo. So far, this would not cause any issue, but once we bump libglib2 and goi, that would cause a circular dependency chain, where goi would depend on cairo, cairo on libglib2, and libglib2 back on goi... However, in goi, cairo is only needed to build some tests, and thus we do not need that dependency, even before we update goi+libglib2. Thanks to Fiona for helping sorting the issue out. Signed-off-by: Yann E. MORIN <[email protected]> Cc: Adam Duskett <[email protected]> Cc: Fiona Klute (WIWA) <[email protected]> Signed-off-by: Thomas Petazzoni <[email protected]>
The homepage has moved, the previous one links to the new URL. Signed-off-by: Fiona Klute (WIWA) <[email protected]> [[email protected]: split into its own patch] Signed-off-by: Yann E. MORIN <[email protected]> Signed-off-by: Thomas Petazzoni <[email protected]>
Since the package was introduced in Buildroot commit 3cb185d, it has been failing to build on !wchar configurations. Let's add the missing dependency on wchar support. Fixes: https://autobuild.buildroot.org/results/f5c543bcf57181373680d0c16a1814d21b000bcf Signed-off-by: Roy Kollen Svendsen <[email protected]> Signed-off-by: Thomas Petazzoni <[email protected]>
Signed-off-by: James Hilliard <[email protected]> Reviewed-by: Marcus Hoffmann <[email protected]> Signed-off-by: Thomas Petazzoni <[email protected]>
Signed-off-by: James Hilliard <[email protected]> Signed-off-by: Thomas Petazzoni <[email protected]>
…l options Since commit a39e0b9 ("package/qt6/qt6base: add support for concurrent module"), we have an explicit option that enables/disables concurrent support, so it no longer makes sense to explicitly disable it unconditionnally first. Signed-off-by: Hannah Kiekens <[email protected]> Signed-off-by: Thomas Petazzoni <[email protected]>
The Ethernet MAC address of the Acqua board is stored in an onboard
EEPROM. Its location is described in the device tree as:
eeprom@58 { // NVMEM node
// EEPROM parameters...
eth0_addr: eth-mac-addr@9A { // NVMEM cells
reg = <0x0 0x06>;
};
};
Since Linux 6.5, defining NVMEM cells this way, as direct children of
the NVMEM node, is deprecated. It is instead recommended to wrap the
cells inside a "fixed-layout" node.
The older, deprecated syntax is still supported on Linux 6.6. Since
Linux 6.7 (commit 2cc3b37f5b6d: "nvmem: add explicit config option to
read old syntax fixed OF cells") however, it is only supported by
selected NVMEM drivers. It is not supported by the at24 driver used to
access the Acqua's onboard EEPROM.
Update the device tree to the new, recommended, syntax. This makes it
work with newer kernels, while preserving compatibility with the
currently used 6.6.30.
Signed-off-by: Edgar Bonet <[email protected]>
Signed-off-by: Thomas Petazzoni <[email protected]>
when pam_lastlog.so is not installed login issues an error that it is not able to load it. Hence only enable the entry when pam_lastlog.so is installed. Fixes: login[649]: PAM unable to dlopen(/lib/security/pam_lastlog.so): /lib/security/pam_lastlog.so: cannot open shared object file: No such file or directory login[649]: PAM adding faulty module: /lib/security/pam_lastlog.so Signed-off-by: Michael Nosthoff <[email protected]> Signed-off-by: Thomas Petazzoni <[email protected]>
This patch fixes a regression [1] introduced in ntpd 4.2.8p18 [2]. ntpd[200]: Listen normally on 3 lo [::1]:123 ntpd[200]: bind(20) AF_INET6 [fe80::bf3d:254d:dee0:d345%3]:123 flags 0x811 failed: Cannot assign requested address ntpd[200]: unable to create socket on enp0s3 (4) for [fe80::bf3d:254d:dee0:d345%3]:123 ntpd[192]: daemon control: got EOF ntpd[192]: daemon child died with signal 11 systemd[1]: ntpd.service: Control process exited, code=exited, status=70/SOFTWARE systemd[1]: ntpd.service: Failed with result 'exit-code'. systemd[1]: Failed to start Network Time Service. If the IPv6 link-local interface was not ready for binding on the first attempt, ntpd would segfault in update_interfaces(). The segfault would only occur when ntpd was started as part of the boot sequence. Most - but not all - boots were affected. Evidently it could happen that the timing of ntpd's start up was delayed enough that the IPv6 link-local interface was ready for the bind() call when it was first issued by open_socket() via create_interface(). [1]: https://bugs.ntp.org/show_bug.cgi?id=3928 [2]: https://bugs.ntp.org/show_bug.cgi?id=3913 Signed-off-by: TIAN Yuanhao <[email protected]> Cc: Bernd Kuhls <[email protected]> Signed-off-by: Thomas Petazzoni <[email protected]>
In the current systemd package, EFI support is tied to enabling systemd-boot, but there are some use cases where EFI support is desired, independently of systemd-boot, for example to mount automatically efivarfs in /sys/firmware/efi/efivars. This commit therefore adds a separate option to enable EFI support. Signed-off-by: Guillaume GC. Chaye <[email protected]> Signed-off-by: Thomas Petazzoni <[email protected]>
This workaround breaks build with gcc 14. Upstream developers acknowledged[1] the 32/64 compatibility issue more than 3 years ago, but no proper fix has been applied. Specifically, for aarch64 we don't even enable BR2_KERNEL_64_USERLAND_32, so this workaround is not effective there. The least we can do is make ebtables depend on !BR2_KERNEL_64_USERLAND_32. [1] https://lore.kernel.org/all/[email protected]/ Fixes: http://autobuild.buildroot.net/results/680674c2b61209b505efa022a8fd9751ddc5fd47/ http://autobuild.buildroot.net/results/60f8f5f087111ec3f300dc7979363de5a9f64f08/ Cc: Thomas De Schampheleire <[email protected]> Signed-off-by: Baruch Siach <[email protected]> Signed-off-by: Thomas Petazzoni <[email protected]>
http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/sys/queue.h?rev=1.70 now returns some HTML soup instead of the plain text version of the file, causing the hash check to fail. http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/sys/queue.h?rev=1.70;content-type=text%2Fplain returns the correct data, but the ";" in the URL causes some issues with the parsing logic in Buildroot. So let's switch to https://raw.githubusercontent.com/NetBSD/src/03be82a6b173b3c62116b7a186067fed3004dd44/sys/sys/queue.h which delivers exactly the same file, but hopefully will be more stable. The file name changed to just queue.h, but the contents is the same. Fixes: http://autobuild.buildroot.net/results/57c8078f382f74859076512425b2f1c52f44e95a/ https://gitlab.com/buildroot.org/buildroot/-/jobs/8199992850 (and many other similar cases) Signed-off-by: Thomas Petazzoni <[email protected]> Signed-off-by: Romain Naour <[email protected]>
The systemd service deployed to the target is derived from an example hardcoded for the /usr/local/sbin/ path, but we install sshguard at /usr/sbin/. Thus, by default we get this error message: $ journalctl -b -u sshguard.service -f systemd[1]: Started SSHGuard - blocks brute-force login attempts. (sshguard)[612]: sshguard.service: Unable to locate executable '/usr/local/sbin/sshguard': No such file or directory (sshguard)[612]: sshguard.service: Failed at step EXEC spawning /usr/local/sbin/sshguard: No such file or directory systemd[1]: sshguard.service: Main process exited, code=exited, status=203/EXEC systemd[1]: sshguard.service: Failed with result 'exit-code'. systemd[1]: sshguard.service: Scheduled restart job, restart counter is at 5. systemd[1]: sshguard.service: Start request repeated too quickly. systemd[1]: sshguard.service: Failed with result 'exit-code'. systemd[1]: Failed to start SSHGuard - blocks brute-force login attempts. Fix up the path in the service after the $(INSTALL) command has run. Signed-off-by: Vladimir Oltean <[email protected]> Signed-off-by: Thomas Petazzoni <[email protected]>
Release notes: https://github.com/stephane/libmodbus/releases/tag/v3.1.11 Signed-off-by: Scott Fan <[email protected]> Signed-off-by: Thomas Petazzoni <[email protected]>
This marks the transitioning of the 22.x releases of nodejs into LTS. [1] LICENSE hash changed due to * various new bundled components[2,3,4] * removed bundled components [5,6] All new components fall under MIT or Apache license which are already mentioned in the license field. All node package tests have been run sucessfully after the update. [1] https://nodejs.org/en/blog/release/v22.11.0 [2] nodejs/node@77936c3 [3] nodejs/node@92439fc [4] nodejs/node@da6c61d [5] nodejs/node@8e4fd28 [6] nodejs/node@20a8c96 Signed-off-by: Marcus Hoffmann <[email protected]> Signed-off-by: Thomas Petazzoni <[email protected]>
When switching the build system to meson in buildroot commit 41ce1cc the way TARGET_NLS_LIBS was passed to the build system was not updated causing build errors. Fixes: http://autobuild.buildroot.net/results/96b/96b08078ea412b97a4719321ad0fdad4003e42c5/ Signed-off-by: Bernd Kuhls <[email protected]> Signed-off-by: Thomas Petazzoni <[email protected]>
…upport Switch to the Bootlin bleeding-edge toolchain since stable toolchain no longer provide Fortran support since 2024.05-1 release [1]. The Fortran support is now optional in toolchain-builder tool and only enabled for bleeding-edge toolchains [2]. [1] https://gitlab.com/buildroot.org/buildroot/-/commit/d3ad58dce9cafccb22d782e56677e060d5eb5a52#428f572a75eed97c0a70da290028c0efb4224a79_545_536 [2] https://gitlab.com/buildroot.org/toolchains-builder/-/commit/a178b246259d92e23679b777fa3d6c166cc424d5 Fixes: (partially) https://gitlab.com/buildroot.org/buildroot/-/jobs/8199992675 Signed-off-by: Romain Naour <[email protected]> Signed-off-by: Thomas Petazzoni <[email protected]>
Bumps to the latest `libspdm 3.5.0` release, this release introduces the optional SPDM 1.3 `GET/SET_KEY_PAIR` support. Which requires an integrator to support additional functionality implemented at link time. Leave this disabled by default as it is optional and so that it does not break build compatibility with integrators. Signed-off-by: Wilfred Mallawa <[email protected]> Signed-off-by: Thomas Petazzoni <[email protected]>
As advocated by Thomas Petazzoni [1], drop bsdiff as it is not maintained anymore. Meanwhile, autobuild also detected that the package was no longer downloadable from the URL, and indeed, Colin Percival, the maintainer, confirmed that he intentionally disabled the package download due to the presence of some security bugs that he doesn't have time to fix. [1] https://patchwork.ozlabs.org/project/buildroot/patch/[email protected]/ Fixes: - http://autobuild.buildroot.org/results/21bb827d3dbf553c79f49d7c184099c75df3d45d Suggested-by: Thomas Petazzoni <[email protected]> Signed-off-by: Dario Binacchi <[email protected]> Signed-off-by: Thomas Petazzoni <[email protected]>
checksec-2.7.1.tar.gz archive was replaced or regenerated by upstream sometime between the 22 September 2024 [1] and the 29 September 2024 [2]. diffoscope report no changes in extracted files exept a different top directory name (checksec.sh-2.7.1/checksec-2.7.1): --- checksec-2.7.1.tar.gz a0d7a444d4603fb3d62fa25ef678e544ef39fa7b3c9bd5d22f1a8c526152cdde +++ checksec-2.7.1.tar.gz eba0616f4033385d6093608a2a2aad3c2debb847d6778c87346f89c80946684f Files identical despite different names --- checksec-2.7.1/ChangeLog +++ checksec.sh-2.7.1/ChangeLog Use the git hash of the 2.7.1 release to use a different archive name than the checksec-2.7.1.tar.gz archive previously released. [1] https://gitlab.com/buildroot.org/buildroot/-/jobs/7888799855 [2] https://gitlab.com/buildroot.org/buildroot/-/jobs/7948006849 Fixes: https://gitlab.com/buildroot.org/buildroot/-/jobs/7948006849 Signed-off-by: Romain Naour <[email protected]> Signed-off-by: Thomas Petazzoni <[email protected]>
The rootfs partition is the first partition, not the second one: the Grub configuration file already contains root=/dev/sda1 by default, and it should be changed to root=/dev/vda1 is Qemu emulation is used. Signed-off-by: Cherniaev Andrei <[email protected]> Signed-off-by: Thomas Petazzoni <[email protected]>
See here for release notes: https://www.zabbix.com/rn/rn7.0.5 Signed-off-by: Waldemar Brodkorb <[email protected]> Signed-off-by: Thomas Petazzoni <[email protected]>
multiple improvements and bugfixes [0] [0] https://git.kernel.org/pub/scm/libs/libgpiod/libgpiod.git/tree/NEWS?h=v2.2 Signed-off-by: Boerge Struempfel <[email protected]> Signed-off-by: Thomas Petazzoni <[email protected]>
The package fails to build on wchar-less uClibc-ng configuration
(i.e. without BR2_TOOLCHAIN_BUILDROOT_WCHAR selected):
```
CC t/unit-tests/unit-test.o
t/unit-tests/clar/clar.c: In function 'clar__assert_equal':
t/unit-tests/clar/clar.c:767:23: error: unknown type name 'wchar_t'
767 | const wchar_t *wcs1 = va_arg(args, const wchar_t *);
| ^~~~~~~
In file included from t/unit-tests/clar/clar.c:13:
t/unit-tests/clar/clar.c:767:58: error: unknown type name 'wchar_t'
767 | const wchar_t *wcs1 = va_arg(args, const wchar_t *);
| ^~~~~~~
t/unit-tests/clar/clar.c:768:23: error: unknown type name 'wchar_t'
768 | const wchar_t *wcs2 = va_arg(args, const wchar_t *);
| ^~~~~~~
t/unit-tests/clar/clar.c:768:58: error: unknown type name 'wchar_t'
768 | const wchar_t *wcs2 = va_arg(args, const wchar_t *);
| ^~~~~~~
t/unit-tests/clar/clar.c:769:65: warning: implicit declaration of function 'wcscmp' [-Wimplicit-function-declaration]
769 | is_equal = (!wcs1 || !wcs2) ? (wcs1 == wcs2) : !wcscmp(wcs1, wcs2);
| ^~~~~~
t/unit-tests/clar/clar.c:784:23: error: unknown type name 'wchar_t'
784 | const wchar_t *wcs1 = va_arg(args, const wchar_t *);
| ^~~~~~~
t/unit-tests/clar/clar.c:784:58: error: unknown type name 'wchar_t'
784 | const wchar_t *wcs1 = va_arg(args, const wchar_t *);
| ^~~~~~~
t/unit-tests/clar/clar.c:785:23: error: unknown type name 'wchar_t'
785 | const wchar_t *wcs2 = va_arg(args, const wchar_t *);
| ^~~~~~~
t/unit-tests/clar/clar.c:785:58: error: unknown type name 'wchar_t'
785 | const wchar_t *wcs2 = va_arg(args, const wchar_t *);
| ^~~~~~~
t/unit-tests/clar/clar.c:787:65: warning: implicit declaration of function 'wcsncmp' [-Wimplicit-function-declaration]
787 | is_equal = (!wcs1 || !wcs2) ? (wcs1 == wcs2) : !wcsncmp(wcs1, wcs2, len);
| ^~~~~~~
make[1]: *** [Makefile:2795: t/unit-tests/clar/clar.o] Error 1
```
This is because since version 2.47.0, Git imports clar unit testing
framework, which uses wchar_t. On wchar-less uClibc-ng configuration,
however, the installed <wchar.h> header is a stub (that is, wchar_t
is undefined).
Apply upstream patchset from Patrick Steinhardt [1], which includes
upstreamed clar build fix.
Fixes: https://autobuild.buildroot.org/results/85dbf87451156fce7c2a12d8882622ea75e0d0db
Link: https://lore.kernel.org/git/[email protected]/ [1]
Signed-off-by: Bagas Sanjaya <[email protected]>
Signed-off-by: Thomas Petazzoni <[email protected]>
The patch bumps U-Boot to version 2024.10. The new version has added EFI Capsule support, which depends on GnuTLS, thus requiring the activation of BR2_TARGET_UBOOT_NEEDS_GNUTLS. Tested on beaglebone black. Signed-off-by: Dario Binacchi <[email protected]> Signed-off-by: Thomas Petazzoni <[email protected]>
Signed-off-by: Wolfram Sang <[email protected]> Signed-off-by: Thomas Petazzoni <[email protected]>
https://github.com/eclipse-zenoh/zenoh-pico/releases/tag/1.0.2 Signed-off-by: Alex Michel <[email protected]> Signed-off-by: Peter Korsgaard <[email protected]>
Signed-off-by: Peter Korsgaard <[email protected]>
Signed-off-by: Peter Korsgaard <[email protected]> (cherry picked from commit a91b9c7) [Peter: drop Makefile change] Signed-off-by: Peter Korsgaard <[email protected]>
Signed-off-by: Peter Korsgaard <[email protected]>
Signed-off-by: Peter Korsgaard <[email protected]> (cherry picked from commit e843fa7) [Peter: drop Makefile/Vagrantfile changes] Signed-off-by: Peter Korsgaard <[email protected]>
Signed-off-by: Peter Korsgaard <[email protected]>
Changelog: https://curl.se/ch/8.11.0.html Fixes CVE-2024-9681: https://curl.se/docs/CVE-2024-9681.html Signed-off-by: Bernd Kuhls <[email protected]> Signed-off-by: Peter Korsgaard <[email protected]>
For the release note, see: http://www.simplesystems.org/libtiff/releases/v4.7.0.html This commit also adds the _SOURCE variable, to switch to the xz archive, which saves ~1.5MB. The _SITE url is also updated to switch to the https protocol. This commit also adds a comment in the hash file about pgp signature veritication. Fixes: - https://nvd.nist.gov/vuln/detail/CVE-2023-6277 - https://nvd.nist.gov/vuln/detail/CVE-2023-52356 - https://nvd.nist.gov/vuln/detail/CVE-2024-7006 Signed-off-by: Julien Olivain <[email protected]> Signed-off-by: Peter Korsgaard <[email protected]>
Release notes: https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/releases CVE-2024-21853 https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01101.html CVE-2024-23918 https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01079.html CVE-2024-24968 https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01097.html CVE-2024-23984 https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01103.html Signed-off-by: Bernd Kuhls <[email protected]> Signed-off-by: Julien Olivain <[email protected]>
For the change log, see [1]. The license hash file changed, due to the year update. See [2]. This commit also adds a comment in the hash file about the pgp signature file source and key id used for the verification. Fixes: - https://nvd.nist.gov/vuln/detail/CVE-2024-37370 - https://nvd.nist.gov/vuln/detail/CVE-2024-37371 [1] https://web.mit.edu/kerberos/www/krb5-1.21/ [2] krb5/krb5@fec2c44 Signed-off-by: Julien Olivain <[email protected]> Signed-off-by: Peter Korsgaard <[email protected]>
Fixes: http://autobuild.buildroot.net/results/52c/52c974e70f922e9d7efea4c538e4438a22faa846/ Signed-off-by: Bernd Kuhls <[email protected]> Co-authored-by: Peter Korsgaard <[email protected]> [https://lists.buildroot.org/pipermail/buildroot/2024-November/767661.html] Signed-off-by: Peter Korsgaard <[email protected]>
For release note, see: https://github.com/linux-nvme/libnvme/releases/tag/v1.11.1 Signed-off-by: Giulio Benetti <[email protected]> Reviewed-by: Vincent Jardin <[email protected]> Signed-off-by: Julien Olivain <[email protected]>
Asaf has privately requested to be removed from the DEVELOPERS file as he will no longer be contributing to Buildroot in the forseeable future. Signed-off-by: Thomas Petazzoni <[email protected]>
I will lose access to my email next week, so hand it over to Leo Yu-Chi Liang. Signed-off-by: Yu Chien Peter Lin <[email protected]> Reviewed-by: Leo Yu-Chi Liang <[email protected]> Signed-off-by: Julien Olivain <[email protected]>
host-skopeo fail to build, using the commands:
echo BR2_PACKAGE_HOST_SKOPEO=y >.config
make olddefconfig
make host-skopeo
This commit fixes the issue by selecting BR2_PACKAGE_HOST_GO
in the Config.in file.
Fixes:
make: *** No rule to make target 'host-', needed by '/buildroot/output/build/host-go-1.23.2/.stamp_configured'. Stop.
Reviewed-by: Yann E. MORIN <[email protected]>
Signed-off-by: Julien Olivain <[email protected]>
Commit 7b2a164 (package/go/go-bin: new host-go provider) broke the case for prompt-less, host-only go packages, as the main host-go symbol would not be selected. This very same use-case was initially broken when the first go-src provider was introduced with fa2536e (package/go: make host package a virtual package), and subsequently fixed in 99a5d51 (package/go: ensure there is a host-go provider), so 7b2a164 is causing a regression of a fixed regression. Fix that the very same way it was originally fixed. Signed-off-by: Yann E. MORIN <[email protected]> Cc: Yann E. MORIN <[email protected]> Cc: Thomas Perale <[email protected]> Signed-off-by: Julien Olivain <[email protected]>
Release notes: https://www.postgresql.org/about/news/postgresql-171-165-159-1414-1317-and-1221-released-2955/ Fixes CVE-2024-10976, CVE-2024-10977, CVE-2024-10978 & CVE-2024-10979. Signed-off-by: Bernd Kuhls <[email protected]> Signed-off-by: Peter Korsgaard <[email protected]>
Changelog: https://www.php.net/ChangeLog-8.php#PHP_8_3 Release notes: https://news-web.php.net/php.announce/444 Fixes CVE-2024-8929, CVE-2024-8932, CVE-2024-11233, CVE-2024-11234 & CVE-2024-11236. Signed-off-by: Bernd Kuhls <[email protected]> Signed-off-by: Julien Olivain <[email protected]>
For change log, see: https://github.com/storaged-project/libblockdev/blob/3.2.1/NEWS.rst Signed-off-by: Giulio Benetti <[email protected]> [Julien: add link to change log] Signed-off-by: Julien Olivain <[email protected]>
…x series Signed-off-by: Bernd Kuhls <[email protected]> Signed-off-by: Peter Korsgaard <[email protected]>
Host bmap-tools runs using host-python3, but did not select it, leading to the confusing situation that BR2_PACKAGE_HOST_PYTHON3=n even though it was built and working. Signed-off-by: Fiona Klute (WIWA) <[email protected]> Signed-off-by: Peter Korsgaard <[email protected]>
{host-}python-sip may fail to install on fast machine, so disable
parallel install.
Fixes:
https://gitlab.com/buildroot.org/buildroot/-/jobs/8350440972 (TestPythonPyQt5)
http://autobuild.buildroot.org/results/8f2/8f24656f3a66d21f2d3c6d6b1adc6bb5f1c0c801 (2024-10-15)
http://autobuild.buildroot.org/results/6e6/6e6bbee714b10e0f04c9d17b7e0ecce057d21d2a (2022-07-15)
Signed-off-by: Romain Naour <[email protected]>
Signed-off-by: Peter Korsgaard <[email protected]>
…t systems Since the bump of util-linux to version 2.40.2 in Buildroot commit f14929c ("package/util-linux: update to 2.40.2"), the build will fail on systems that are not Y2038, such as uClibc configurations. In order to preserve the previous behavior, pass --disable-year2038. See the gnulib documentation for details [1]. Contrary to what the option name might suggest, it doesn't really disable Y2038 support, but only the check that the system is Y2038 compliant. So even with --disable-year2038, if the system is Y2038 compliant (uses a 64-bit arch, uses the musl C library, or uses the glibc C library with BR2_TIME_BITS_64=y), util-linux tools will be Y2038 compliant. "--disable-year2038" was already added to util-linux in commit 11ae90b "package/util-linux: allowing building even on non-Y2038 compliant systems". Fixes: https://autobuild.buildroot.org/results/630fc287deb1cf5a684f274058b918a5d7aef989 [1] https://www.gnu.org/software/gnulib/manual/html_node/Avoiding-the-year-2038-problem.html Reviewed-by: Vincent Jardin <[email protected]> Signed-off-by: Julien Olivain <[email protected]> Signed-off-by: Peter Korsgaard <[email protected]>
Signed-off-by: Peter Korsgaard <[email protected]>
We migrated to Gitlab a while ago, so update the CHANGES links to point to that rather than git.buildroot.net. Automated with: sed -i 's|http://git.buildroot.net/buildroot/plain/CHANGES?id=\([^"]*\)|https://gitlab.com/buildroot.org/buildroot/-/blob/\1/CHANGES|g' \ docs/website/news.html Signed-off-by: Peter Korsgaard <[email protected]>
Signed-off-by: Peter Korsgaard <[email protected]>
Fixes https://autobuild.buildroot.org/results/54a/54a165827f536be47cd45c98da3937a1e94a7c65/ Upstream is no longer accessible, so use s.b.n instead. Signed-off-by: Peter Korsgaard <[email protected]> Signed-off-by: Julien Olivain <[email protected]>
The Config.in help string for BR2_FORTIFY_SOURCE_{2,3} mention
"_FORTIFY_SOURCES" (plural, with an extra "S"). The correct macro name
is "_FORTIFY_SOURCE" (without the "S"). See [1].
This commit fixes those typos.
[1] https://www.gnu.org/software/libc/manual/html_node/Source-Fortification.html
Signed-off-by: Julien Olivain <[email protected]>
Reviewed-by: Vincent Jardin <[email protected]>
Signed-off-by: Peter Korsgaard <[email protected]>
Signed-off-by: Bernd Kuhls <[email protected]> Signed-off-by: Peter Korsgaard <[email protected]>
Doxygen source archive download fails with a HTTP 404 Not Found error. The doxygen download page [1] mention that older versions can be downloaded on SourceForge at [2]. This commit fixes the issue by changing _SITE to this new URL. Fixes: https://autobuild.buildroot.org/results/253450bf374ce858fe12712059c435fc773d52f8 [1] https://www.doxygen.nl/download.html [2] https://sourceforge.net/projects/doxygen/files/ Signed-off-by: Julien Olivain <[email protected]> Signed-off-by: Peter Korsgaard <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Update to buildroot in preparation to switch freedom-u-sdk over to replace riscv-gnu-toolchain with the toolchain supported in buildroot, which builds faster using upstream sources and takes less space.