a0871be6c0
* Update buildroot-patches for 2020.11-rc1 buildroot * Update buildroot to 2020.11-rc1 Signed-off-by: Stefan Agner <stefan@agner.ch> * Don't rely on sfdisk --list-free output The --list-free (-F) argument does not allow machine readable mode. And it seems that the output format changes over time (different spacing, using size postfixes instead of raw blocks). Use sfdisk json output and calculate free partition space ourselfs. This works for 2.35 and 2.36 and is more robust since we rely on output which is meant for scripts to parse. * Migrate defconfigs for Buildroot 2020.11-rc1 In particular, rename BR2_TARGET_UBOOT_BOOT_SCRIPT(_SOURCE) to BR2_PACKAGE_HOST_UBOOT_TOOLS_BOOT_SCRIPT(_SOURCE). * Rebase/remove systemd patches for systemd 246 * Drop apparmor/libapparmor from buildroot-external * hassos-persists: use /run as directory for lockfiles The U-Boot tools use /var/lock by default which is not created any more by systemd by default (it is under tmpfiles legacy.conf, which we no longer install). * Disable systemd-update-done.service The service is not suited for pure read-only systems. In particular the service needs to be able to write a file in /etc and /var. Remove the service. Note: This is a static service and cannot be removed using systemd-preset. * Disable apparmor.service for now The service loads all default profiles. Some might actually cause problems. E.g. the profile for ping seems not to match our setup for /etc/resolv.conf: [85503.634653] audit: type=1400 audit(1605286002.684:236): apparmor="DENIED" operation="open" profile="ping" name="/run/resolv.conf" pid=27585 comm="ping" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
33 lines
1.2 KiB
Diff
33 lines
1.2 KiB
Diff
Subject: [PATCH] Work around bool type redefinition by altivec
|
|
|
|
On powerpc64le, the SDL header may include altivec.h and this
|
|
(combined with -std=c99) will cause a compile failure due to bool
|
|
being redefined as a vector type.
|
|
|
|
Adjust the compiler flags to add -std=gnu99 (which is compatible with
|
|
altivec) when using gcc. The generic flag '-std=c99' is left in place for other
|
|
compilers (in the gcc case it is overridden by the (later) gnu flag).
|
|
|
|
Signed-off-by: Sam Bobroff <sam.bobroff@au1.ibm.com>
|
|
---
|
|
waftools/detections/compiler.py | 3 ++-
|
|
1 file changed, 2 insertions(+), 1 deletion(-)
|
|
|
|
diff --git a/waftools/detections/compiler.py b/waftools/detections/compiler.py
|
|
index 5bbba87..50836a2 100644
|
|
--- a/waftools/detections/compiler.py
|
|
+++ b/waftools/detections/compiler.py
|
|
@@ -43,7 +43,8 @@ def __add_gcc_flags__(ctx):
|
|
"-Wno-switch", "-Wparentheses", "-Wpointer-arith",
|
|
"-Wno-pointer-sign",
|
|
# GCC bug 66425
|
|
- "-Wno-unused-result"]
|
|
+ "-Wno-unused-result",
|
|
+ "-std=gnu99"]
|
|
|
|
def __add_clang_flags__(ctx):
|
|
ctx.env.CFLAGS += ["-Wno-logical-op-parentheses", "-fcolor-diagnostics",
|
|
--
|
|
2.10.0.297.gf6727b0
|
|
|