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
38 lines
1.2 KiB
Diff
38 lines
1.2 KiB
Diff
Disable fenv.h in certain configurations
|
|
|
|
The boost build system does not properly test whether fenv.h is
|
|
available, and if it is, if it supports all the features used by
|
|
Boost. This causes build failures with uClibc (reported upstream at
|
|
https://svn.boost.org/trac/boost/ticket/11756) but also with glibc on
|
|
specific architectures that don't have a full fenv implementation,
|
|
such as NIOSII or Microblaze.
|
|
|
|
To address this, we forcefully disable the use of fenv support in the
|
|
affected configurations.
|
|
|
|
Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
|
|
[Thomas: add Microblaze/NIOSII exclusions.]
|
|
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
|
|
|
|
Index: b/boost/config/platform/linux.hpp
|
|
===================================================================
|
|
--- a/boost/config/platform/linux.hpp
|
|
+++ b/boost/config/platform/linux.hpp
|
|
@@ -48,6 +48,16 @@
|
|
#endif
|
|
|
|
//
|
|
+// uClibc has no support for fenv.h, and also a few architectures
|
|
+// don't have fenv.h support at all (or incomplete support) even with
|
|
+// glibc.
|
|
+
|
|
+//
|
|
+#if defined(__UCLIBC__) || defined(__nios2__) || defined(__microblaze__)
|
|
+# define BOOST_NO_FENV_H
|
|
+#endif
|
|
+
|
|
+//
|
|
// If glibc is past version 2 then we definitely have
|
|
// gettimeofday, earlier versions may or may not have it:
|
|
//
|