- Nov 16, 2022
-
-
Peter Korsgaard authored
Signed-off-by:Peter Korsgaard <peter@korsgaard.com>
-
- Nov 14, 2022
-
-
Neal Frager authored
This patch fixes the kv260.sh to generate a working u-boot.itb now that the CONFIG_MULTI_DTB_FIT u-boot option is no longer used. This is a follow-up fix of 515319b8 ("board/zynqmp/kria/kv260/uboot.fragment: remove unnecessary CONFIG_MULTI_DTB_FIT option") to fix the build of: https://gitlab.com/buildroot.org/buildroot/-/jobs/3310463281 Signed-off-by:
Neal Frager <neal.frager@amd.com> Signed-off-by:
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
-
- Nov 13, 2022
-
-
Fabrice Fontaine authored
libvncclient v0.9.13 was discovered to contain a memory leak via the function rfbClientCleanup(). Signed-off-by:
Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by:
-
Fabrice Fontaine authored
- Refresh patch - Drop -lz from Makefile with libressl as this is the only solution for now: https://github.com/radiator-software/p5-net-ssleay/issues/399 - License has been clarified to be Artistic-2.0 since version 1.86.11: https://github.com/radiator-software/p5-net-ssleay/commit/aa4a0206d6d2a5ac2998dd9d6a8c5b88902c04de - This bump will fix the following build failure with libressl: In file included from /home/autobuild/autobuild/instance-11/output-1/host/armeb-buildroot-linux-uclibcgnueabi/sysroot/usr/lib/perl5/5.34.1/armeb-linux/CORE/perl.h:5748, from SSLeay.xs:141: SSLeay.xs: In function 'XS_Net__SSLeay_SESSION_get_master_key': SSLeay.xs:5569:37: error: invalid use of incomplete typedef 'SSL_SESSION' {aka 'struct ssl_session_st'} 5569 | sv_setpvn(ST(0), (const char*)s->master_key, s->master_key_length); | ^~ https://metacpan.org/release/CHRISN/Net-SSLeay-1.93_01/changes Fixes: - http://autobuild.buildroot.org/results/71337cc496727f2b1173c055d706c5bfc2f5d2bc Signed-off-by:
-
Bernd Kuhls authored
Fixes: http://autobuild.buildroot.net/results/9710753984a38b8c6f83a136b39c3bc320ba558b/ Signed-off-by:
Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by:
-
Thomas Petazzoni authored
When BR2_XTENSA_CUSTOM=y is used with the internal toolchain, an overlay file is mandatory, which genrandconfig can't provide. So we simply disallow such configurations. Signed-off-by:
Yann E. MORIN <yann.morin.1998@free.fr>
-
Thomas Petazzoni authored
Commit 4cbf7336 ("arch/xtensa: custom configuration requires an overlay") added a check in arch/arch.mk.xtensa to bail out if a custom Xtensa core is selected but not overlay file is provided. While this is indeed a perfectly valid check to make when building an internal toolchain, with an external toolchain it's entirely possible to build with no overlay file: the toolchain already exists, and there's no overlay to be applied in the context of the Buildroot build. And indeed commit 4cbf7336 broke some of the runtime test cases that use a custom Xtensa core configuration, with no overlay, to test the toolchains.bootlin.com Xtensa external toolchain. By relaxing the check to only apply to internal toolchain configurations, we fix those test cases. It is to be noted that this still allows a configuration where gdb gets built for a custom core, but with no overlay, so basically that means the fsf variant, which can lead to build or run failures that 4cbf7336 attempted to fix to begin with. This still covers the most common cases. Finally, it also means being able to build a kernel with no overlay, but this is offset by the fact that the kernel may be already patched with an overlay (as it is possible to specify a custom kernel), which is most probably what people using a custom core would have. Fixes: https://gitlab.com/buildroot.org/buildroot/-/jobs/3282261966 https://gitlab.com/buildroot.org/buildroot/-/jobs/3282261963 Signed-off-by:
-
Fabrice Fontaine authored
Fix CVE-2022-40284: A buffer overflow was discovered in NTFS-3G before 2022.10.3. Crafted metadata in an NTFS image can cause code execution. A local attacker can exploit this if the ntfs-3g binary is setuid root. A physically proximate attacker can exploit this if NTFS-3G software is configured to execute upon attachment of an external storage device. https://github.com/tuxera/ntfs-3g/security/advisories/GHSA-v4w8-jv3w-7prm https://github.com/tuxera/ntfs-3g/releases/tag/2022.10.3 Signed-off-by:
-
Yann E. MORIN authored
Since v14 in 2018, audit support has needed libcap-ng. Fixes: http://autobuild.buildroot.org/results/43abdb85cc2f386d427cec1cfa876e20e3509cb8/ Signed-off-by: -
Yann E. MORIN authored
dracut is not really ready to be installed with a non-/ prefix, and it has a lot of hard-coded assumptions that it is going to run on the host for which it is goign to generate an initramfs; for example, it hard-codes calls to /lib/dracut/some-file in some of its modules. It also uses the host system layout to decide whether it needs a merged-usr or not. Furthermore, dracut populates the temporary directory which content will be used to generate the cpio, with a bunch of files, even before calling any of the dracut modules. The name for that temporary directory is not predictable (looks like the output of 'mktemp -d dracut.XXXXXX', with names like dracut.1Vfn9F seen while debugging). As a consequence, we can't prepare the temporary directory with the proper symlinks beforehand. So, we provide a very-early module of our own, that will (hopefully) run before any other module, to fixup the messed-up layout prepared by dracut. This module moves the content of /lib, /bin, and /sbin, out and into their counterparts in /usr, and creates the usual symlinks. When we do not require a merged-usr, then we have nothing to do, so the module checks for /lib being a symlink, as the hint that we want a merged-usr or not. Note: currently, we've seen nothing that dracut installed in /bin or /sbin, but for trying to be future-proof, we also handle them; this causes a spurious warning: mv: cannot stat '..../build/buildroot-fs/cpio/tmp/dracut.YQnzNP/initramfs/bin/*': No such file or directory Since there are already quite a bunch of similar failures in the official modules bundled in dracut, an extra such issue or two should not be too scary... Fixes: https://gitlab.com/buildroot.org/buildroot/-/jobs/3282261241 https://gitlab.com/buildroot.org/buildroot/-/jobs/3282261239 https://gitlab.com/buildroot.org/buildroot/-/jobs/3282261236 Signed-off-by: -
Yann E. MORIN authored
systemd does not build with -Ofast (at least with gcc-12), leading to build errors like: ../src/shared/condition.c: In function ‘condition_dump_list’: ../src/shared/condition.c:1227:33: error: ‘%s’ directive argument is null [-Werror=format-overflow=] 1227 | "%s\t%s: %s%s%s %s\n", | ^~ cc1: some warnings being treated as errors It is not really clear what the reason is, but it smells like a compiler error. Indeed, the failing format is passed to an fprintf, and the parameter corresponding to the failing %s directive is a call to a function which prototype is defined but the implementation only comes later in the same compilation unit, but is the result of macro expansion, which yields a function definition like: const char foo_to_string(foo_type i) { if (i < 0 || i >= (foo_type) ELEMENTSOF(foo_table)) return NULL; return foo_table[i] } (where ELEMENTSOF(x) is a macros arounf sizeof(x) to determine the number of elements in the array foo_table). However, in the failing case, foo_table is a static const array indexed with constants from an enum, and foo_to_string() is only ever called with variables that are only ever set to one of those enum values. Since -Ofast is also explicitly documented as breaking otehrwise conformant programs, we're not going to debug further the reason for the build failure. Instead, just revert to the best alternate optimisation level. We chose -O3, as -Ofast is based on -O3 with breaking optimisation flags. With -O3, the build succeeds. Fixes: http://autobuild.buildroot.org/results/3ffaa9b3ecacc6ac326be78196af1ad613f195ed/ (sparc64) http://autobuild.buildroot.org/results/3f6ae2e503dd1539e4240f344865da4881879204/ (arm) http://autobuild.buildroot.org/results/68c17056490d441c7f862349e9c7e471b4570162/ (ppc64) ... Signed-off-by: -
Yann E. MORIN authored
matchbox-startup-monitor is an ageing package, and uses an old configure.ac with archaic constructs. This had generated a configure script that incorrectly tries to look for and validate a C++ compiler: checking for powerpc64le-buildroot-linux-gnu-g++... no checking whether we are using the GNU C++ compiler... no checking whether no accepts -g... no checking dependency style of no... none checking how to run the C++ preprocessor... /lib/cpp configure: error: C++ preprocessor "/lib/cpp" fails sanity check Calling autoreconf fixes the issue, as the generated configure no longer tries to look for a C++ compiler at all anymore. Running autoreconf does not add any new dependency, as they are already in the dependency chain via other packages. Fixes: http://autobuild.buildroot.org/results/223/223f43dd76ee907c5f25c4fee94a0f5d75614dd5/ See also similar changes: 9993a36f package/pamtester: fix build without C++ c05cc5de package/madplay: needs autoreconf eae18d01 libmad: needs autoreconf 43274dd3 package/libid3tag: needs autoreconf Signed-off-by: -
Neal Frager authored
This patch removes the CONFIG_MULTI_DTB_FIT u-boot option for the zynqmp_kria_kv260_defconfig as it is not necessary. The post build kv260.sh creates the proper u-boot.itb without needing this option. Fixes: https://gitlab.com/buildroot.org/buildroot/-/jobs/3310463281 Signed-off-by:
-
Baruch Siach authored
ATF version 2.2 and older does not disable SSP when ENABLE_STACK_PROTECTOR is not set. This is because the compiler enables SSP by default, and ATF does not pass -fno-stack-protector to the compiler. Upstream commit 7af195e29a42 ("Disable stack protection explicitly") fixed the issue for v2.3 and newer. Add -fno-stack-protector in CFLAGS when BR2_TARGET_ARM_TRUSTED_FIRMWARE_SSP is not set to fix older ATF versions. Fixes: https://gitlab.com/buildroot.org/buildroot/-/jobs/3301821171 Cc: Dick Olsson <hi@senzilla.io> Cc: Sergey Matyukevich <geomatsi@gmail.com> Signed-off-by:Baruch Siach <baruch@tkos.co.il> Signed-off-by:
-
Fabrice Fontaine authored
Fix the following build failure raised since the addition of the package in commit 8fdf8731: mdio.c: In function 'mdio_modprobe': mdio.c:738:15: error: implicit declaration of function 'fork' [-Werror=implicit-function-declaration] 738 | pid = fork(); | ^~~~ Fixes: - http://autobuild.buildroot.org/results/c53aaeaa34dd4d6d9a57da196687beecaeed9fe2 Signed-off-by:
Joachim Wiberg <troglobit@gmail.com> Signed-off-by:
-
Thomas Petazzoni authored
Since upstream commit https://github.com/ImageMagick/ImageMagick/commit/07f3b487f9860fd4eb9422f1a906d0fe83b6fd1c (which first appeared in version 7.1.0-47), ImageMagick forces the need of a C++ compiler to build its utilities. Despite the request of Bernd Kuhls to revert this change, upstream declined. Since this change is causing build failures in our autobuilders, our only choice is to follow the choice of upstream, and disable building the utilities when C++ support is not available. Fixes: http://autobuild.buildroot.net/results/4283235d697408cf2e70be5e3769dbe6ebb9ddae/ Signed-off-by:
-
Nuno Gonçalves authored
sudo's configure script looks up on the host to determine the path where to install its systemd tmpfiles. That is incorrect in cross-compilation. We can explicitly tell sudo where to install its tmpfiles, which we do when systemd is enabled (in Buildroot, systemd-tmpfiles is always enabled when systemd is), or we can tell it not to install tmpfiles at all, which we do otherwise. Signed-off-by:
Nuno Gonçalves <nunog@fr24.com> [yann.morin.1998@free.fr: reword and extend commit log] Signed-off-by:
-
Nuno Gonçalves authored
sudo's configure script looks up on the host to determine the path to the timezone data location. That fails in cross-compilation. This is used to sanitise the TZ envirnment variable at runtime, and is not used at buildtime (except to be stored as a string in the program). We can tell sudo where the tz data will be, which we do when the tzdata package is enabled, and we can tell it not to use it at all (to not pass TZ down to sudo-ed executions) othwerwise. Signed-off-by:
-
Heiko Thiery authored
Commit 223516b5 (configs/kontron_bl_imx8mm: U-Boot needs util-linux) added the needed dependency against host-util-linux, but missed an earlier comment about u-boot still failing [0] The U-Boot makefile for the host tools does not handle the compiler/linker options properly. There are some patches [1][2] that fixes that issue already applied in the newer U-Boot version 2022.10. So we have to bump U-Boot to fix an autobuilder failure. Fixes: https://gitlab.com/buildroot.org/buildroot/-/jobs/3267233833 [0] https://lore.kernel.org/buildroot/CAEyMn7Y3UgT-8dYY5rbnzcPfbGmqRVXG=joWx1fSSCC=WiFzbg@mail.gmail.com/ [1] U-Boot: a638bd349ea43825 (kbuild: add KBUILD_HOSTLDFLAGS to cmd_host-csingle) [2] U-Boot: 31a7688cbe0ed5ed (tools: mkeficapsule: use pkg-config to get -luuid and -lgnutls) Cc: Yann E. MORIN <yann.morin.1998@free.fr> Signed-off-by:
Heiko Thiery <heiko.thiery@gmail.com> [yann.morin.1998@free.fr: - update commit log with reference to [0] - slightly tweak commit log ] Signed-off-by:
-
Erico Nunes authored
Backport upstream patch to fix build with musl libc. This patch is only a requirement since efivar 38 and was applied upstream shortly after the 38 version tag. Fixes: http://autobuild.buildroot.net/results/c49d894b109d68e2624074eab8b939fefa3b42ef/ Signed-off-by:
Erico Nunes <nunes.erico@gmail.com> Signed-off-by:
-
- Nov 11, 2022
-
-
Fabrice Fontaine authored
Fix the following build failure raised since bump to version 0.9.4 in commit 5cae1a0d: In file included from iw_if.h:26:0, from conf.c:19: /home/buildroot/autobuild/instance-1/output-1/host/mips-buildroot-linux-gnu/sysroot/usr/include/linux/if.h:71:2: error: redeclaration of enumerator 'IFF_UP' IFF_UP = 1<<0, /* sysfs */ ^ /home/buildroot/autobuild/instance-1/output-1/host/mips-buildroot-linux-gnu/sysroot/usr/include/net/if.h:44:5: note: previous definition of 'IFF_UP' was here IFF_UP = 0x1, /* Interface is up. */ ^ Fixes: - http://autobuild.buildroot.org/results/cbdf3e0cf0bee8f1b076581768c24155afc320d9 Signed-off-by:
-
Bernd Kuhls authored
This is a follow-up patch for https://git.busybox.net/buildroot/commit/?id=28497102e1788df3628bd3324a3304a03c7942d0 which created a new option for topology support in alsa-lib, this dependency was not ported over to alsa-utils. Fixes: http://autobuild.buildroot.net/results/a9c9f5157365efe8271bf69dab0d5a5532b196ea/ Signed-off-by:
-
Fabrice Fontaine authored
Fix the following systemd build failure raised since bump to version 5.0.1 in commit db199980: ../src/lxc/cgroups/cgfsng.c: In function 'unpriv_systemd_create_scope': ../src/lxc/cgroups/cgfsng.c:1234:104: error: incompatible type for argument 10 of 'sd_bus_call_method_asyncv' r = sd_bus_call_method_asyncv(bus, NULL, DESTINATION, PATH, INTERFACE, "Subscribe", NULL, NULL, NULL, NULL); ^~~~ Fixes: - https://gitlab.com/buildroot.org/buildroot/-/jobs/3282261449 Signed-off-by:
-
Thomas Petazzoni authored
Commit 4e7dfe20 ("configs/friendlyarm_nanopi_m4: remove defconfig") forgot to fully reflect the removal of the defconfig in the DEVELOPERS file, causing a get-developers warning: WARNING: 'board/friendlyarm/nanopi-m4' doesn't match any file Signed-off-by:
-
Thomas Petazzoni authored
Fixes: /usr/bin/ld: cannot find -lgnutls /usr/bin/ld: cannot find -luuid collect2: error: ld returned 1 exit status when building U-Boot. Fixes: https://gitlab.com/buildroot.org/buildroot/-/jobs/3301821264 Signed-off-by:
-
Thomas Petazzoni authored
This defconfig has been failing to build for several months, with nobody stepping up to fix it. It's time to drop it. See https://lore.kernel.org/buildroot/20220806224338.0159e15c@windsurf/ for a notification on August 6, 2022 about the issues with this defconfig. Fixes: https://gitlab.com/buildroot.org/buildroot/-/jobs/3259671399 Cc: Suniel Mahesh <sunil@amarulasolutions.com> Signed-off-by:
-
Thomas Petazzoni authored
This defconfig has been failing to build for several months, with nobody stepping up to fix it. It's time to drop it. See https://lore.kernel.org/buildroot/20220806224338.0159e15c@windsurf/ for a notification on August 6, 2022 about the issues with this defconfig. Fixes: https://gitlab.com/buildroot.org/buildroot/-/jobs/3259671395 Cc: Suniel Mahesh <sunil@amarulasolutions.com> Signed-off-by:
-
Thomas Petazzoni authored
This defconfig has been failing to build for several months, with nobody stepping up to fix it. It's time to drop it. See https://lore.kernel.org/buildroot/20220806224338.0159e15c@windsurf/ for a notification on August 6, 2022 about the issues with this defconfig. Fixes: https://gitlab.com/buildroot.org/buildroot/-/jobs/3259671226 Cc: Suniel Mahesh <sunil@amarulasolutions.com> Signed-off-by:
-
- Nov 09, 2022
-
-
Wolfgang Grandegger authored
The name of the tool in udisks2 is udisksctl. Signed-off-by:
Wolfgang Grandegger <wg@grandegger.com> Signed-off-by:
-
- Nov 08, 2022
-
-
Thomas Petazzoni authored
Commit ea38acd1 ("package/boost: backport development branch changes to fix MIPS64 build failure") introduced a patch formatting issue detected by check-package. This commit fixes this issue. Fixes: package/boost/0001-Improve-modfunc-performance.patch:4: generate your patches with 'git format-patch -N' https://gitlab.com/buildroot.org/buildroot/-/jobs/3287511158 Signed-off-by:
-
Fabrice Fontaine authored
Fix the following musl build failure (disabling -Werror seems to be the only "solution": https://github.com/smuellerDD/libkcapi/issues/136): lib/kcapi-kernel-if.c: In function '_kcapi_common_send_meta': lib/kcapi-kernel-if.c:212:12: error: unsigned conversion from 'long int' to 'long unsigned int' changes value from '-4' to '4294967292' [-Werror=sign-conversion] 212 | header = CMSG_NXTHDR(&msg, header); | ^~~~~~~~~~~ Fixes: - http://autobuild.buildroot.org/results/c789d43e71e6075e297bef58d888228a89055bbc Signed-off-by:
-
- Nov 07, 2022
-
-
Fabrice Fontaine authored
This bump will fix the following build failure raised since bump of skalibs to version 2.12.0.1 in commit 0f7bfc80 thanks to https://github.com/skarnet/s6-linux-init/commit/6696cee3bd309f61fc6c945ef747262a845e9267 In file included from src/shutdown/hpr_shutdown.c:8: src/shutdown/hpr.h:20:40: error: unknown type name 'tain_t'; did you mean 'tain'? 20 | extern int hpr_shutdown (unsigned int, tain_t const *, unsigned int) ; | ^~~~~~ | tain Update hash of COPYING (update in year with https://github.com/skarnet/s6-linux-init/commit/42a91a98b780759257862642c764c2102237fea6) https://github.com/skarnet/s6-linux-init/blob/v1.0.8.0/NEWS Fixes: - http://autobuild.buildroot.org/results/4382beeb0f94d583ba605c70a47f34b45c76e311 Signed-off-by:
-
Fabrice Fontaine authored
Fix the following build failure raised since bump to version 5.0.1 in commit db199980: Run-time dependency systemd found: NO (tried pkgconfig and cmake) ../output-1/build/lxc-5.0.1/config/init/systemd/meson.build:11:4: ERROR: Dependency "systemd" not found, tried pkgconfig and cmake Fixes: - http://autobuild.buildroot.org/results/495175c367084093bc01c40290736c738d876894 Signed-off-by:
-
Fabrice Fontaine authored
Fix the following uclibc build failure raised since bump to version 1.4.0 in commit 06a9dc35 and https://github.com/smuellerDD/libkcapi/commit/12f19b9a1dd308117f83e8cb33e28e3c040710a0: lib/kcapi-kernel-if.c: In function '_kcapi_common_send_meta': lib/kcapi-kernel-if.c:196:26: error: conversion to 'int' from 'size_t' {aka 'unsigned int'} may change the sign of the result [-Werror=sign-conversion] 196 | msg.msg_iovlen = kcapi_downcast_int(iovlen); | ^~~~~~~~~~~~~~~~~~ Fixes: - http://autobuild.buildroot.org/results/eccf4b84670b5ef0fdd68b46338edf5043c7cc0d Signed-off-by:
-
Fabrice Fontaine authored
Fix the following per-package build failure raised since commit 82480ee2: configure.ac:44: error: possibly undefined macro: AC_SEARCH_LIBS If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. Fixes: - http://autobuild.buildroot.org/results/ecf72cd1ebd53f3b3b10f0a24082f9c0ab5d4d12 Signed-off-by:
-
Fabrice Fontaine authored
Pass TARGET_LDFLAGS (which contains -static) to fix the following static build failures with gpio, iio and pci: LINK lsgpio /home/autobuild/autobuild/instance-8/output-1/host/lib/gcc/arm-buildroot-linux-musleabi/10.4.0/../../../../arm-buildroot-linux-musleabi/bin/ld: /home/autobuild/autobuild/instance-8/output-1/host/lib/gcc/arm-buildroot-linux-musleabi/10.4.0/libgcc.a(_dvmd_lnx.o): in function `__aeabi_ldiv0': /home/autobuild/autobuild/instance-8/output-1/build/host-gcc-final-10.4.0/build/arm-buildroot-linux-musleabi/libgcc/../../../libgcc/config/arm/lib1funcs.S:1499: undefined reference to `raise' [...] LINK iio_event_monitor /home/thomas/autobuild/instance-2/output-1/host/lib/gcc/microblazeel-buildroot-linux-musl/11.3.0/../../../../microblazeel-buildroot-linux-musl/bin/ld: /home/thomas/autobuild/instance-2/output-1/host/lib/gcc/microblazeel-buildroot-linux-musl/11.3.0/libgcc.a(unwind-dw2.o): in function `size_of_encoded_value': /home/thomas/autobuild/instance-2/output-1/build/host-gcc-final-11.3.0/build/microblazeel-buildroot-linux-musl/libgcc/../../../libgcc/unwind-pe.h:88: undefined reference to `abort' Fixes: - http://autobuild.buildroot.org/results/f202eb843ef331939f5f12325bdbf2d0d664a7ce - http://autobuild.buildroot.org/results/504ec8be1ebd15c5da09f8b90bb723a58d4c58c5 Signed-off-by:
-
Fabrice Fontaine authored
Fix the following static build failure with popt and iconv raised since bump to version 1.0.9 in commit 69015ce9 and https://sourceforge.net/p/gptfdisk/code/ci/122b58ad82f1a144226d262c87241ee035ed1aff (which added an unified Makefile): /home/autobuild/autobuild/instance-0/output-1/host/bin/mips64el-buildroot-linux-uclibc-g++ crc32.o support.o guid.o gptpart.o mbrpart.o basicmbr.o mbr.o gpt.o bsd.o parttypes.o attributes.o diskio.o diskio-unix.o sgdisk.o gptcl.o -static -liconv -lpopt -o sgdisk /home/autobuild/autobuild/instance-0/output-1/host/lib/gcc/mips64el-buildroot-linux-uclibc/11.3.0/../../../../mips64el-buildroot-linux-uclibc/bin/ld: /home/autobuild/autobuild/instance-0/output-1/host/mips64el-buildroot-linux-uclibc/sysroot/usr/lib64/../lib64/libpopt.a(poptint.o): in function `strdup_locale_from_utf8': poptint.c:(.text+0x113c): undefined reference to `libiconv_open' As can be seen above, this build failure is raised because -liconv is added before -lpopt so use pkgconfig and SGDISK_LDLIBS The addition of -liconv in LDLIBS could probably be removed in a follow-up patch for next branch Fixes: - http://autobuild.buildroot.org/results/c9f2c9e737c2dd1cd4c1a08a5e8a48165179282d Signed-off-by:
-
Andreas Ziegler authored
Backport from Boost/intrusive development branch. Fixes issue introduced with version 1.80. Issue: https://github.com/boostorg/intrusive/issues/79 Fixes: http://autobuild.buildroot.net/results/6cb/6cbc0672f3c5046405793d8cdc8f961d2ffb1d3e Signed-off-by:
Andreas Ziegler <br015@umbiko.net> Signed-off-by:
-
Thomas Petazzoni authored
This defconfig has been failing to build for several months, with nobody stepping up to fix it. It's time to drop it. See https://lore.kernel.org/buildroot/20220806224338.0159e15c@windsurf/ for a notification on August 6, 2022 about the issues with this defconfig. Fixes: https://gitlab.com/buildroot.org/buildroot/-/jobs/3234499145 Cc: Jagan Teki <jagan@amarulasolutions.com> Signed-off-by:
-
Thomas Petazzoni authored
This defconfig has been failing to build for several months, with nobody stepping up to fix it. It's time to drop it. See https://lore.kernel.org/buildroot/20220806224338.0159e15c@windsurf/ for a notification on August 6, 2022 about the issues with this defconfig. Fixes: https://gitlab.com/buildroot.org/buildroot/-/jobs/3234499144 Cc: Suniel Mahesh <sunil@amarulasolutions.com> Signed-off-by:
-
