From: Fabrice Fontaine <fontaine.fabrice@gmail.com>
To: buildroot@buildroot.org
Cc: Romain Naour <romain.naour@gmail.com>,
Fabrice Fontaine <fontaine.fabrice@gmail.com>
Subject: [Buildroot] [PATCH v2, 1/2] package/glibc: can't be built with Optimize for fast
Date: Sun, 15 May 2022 11:02:28 +0200 [thread overview]
Message-ID: <20220515090229.395668-1-fontaine.fabrice@gmail.com> (raw)
Fix the following build failure:
In file included from <command-line>:
./../include/libc-symbols.h:82:3: error: #error "glibc must not be compiled with -ffast-math"
82 | # error "glibc must not be compiled with -ffast-math"
| ^~~~~
Fixes:
- http://autobuild.buildroot.org/results/3d91f3685ae6c3e1f765d419ea2c0da4cb0eb3be
Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
---
Changes v1 -> v2 (after review of Yann E. Morin):
- Force -O2 instead of disabling gcc
package/glibc/glibc.mk | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/package/glibc/glibc.mk b/package/glibc/glibc.mk
index 7b46ad42c3..45155fdc28 100644
--- a/package/glibc/glibc.mk
+++ b/package/glibc/glibc.mk
@@ -118,6 +118,11 @@ ifeq ($(BR2_nios2),y)
GLIBC_CFLAGS += -O2
endif
+# glibc can't be built with Optimize for fast
+ifeq ($(BR2_OPTIMIZE_FAST),y)
+GLIBC_CFLAGS += -O2
+endif
+
define GLIBC_CONFIGURE_CMDS
mkdir -p $(@D)/build
# Do the configuration
--
2.35.1
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2022-05-15 9:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-15 9:02 Fabrice Fontaine [this message]
2022-05-15 9:02 ` [Buildroot] [PATCH v2, 2/2] package/glibc: can't be built without optimization Fabrice Fontaine
2022-05-16 21:47 ` [Buildroot] [PATCH v2, 1/2] package/glibc: can't be built with Optimize for fast Yann E. MORIN
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220515090229.395668-1-fontaine.fabrice@gmail.com \
--to=fontaine.fabrice@gmail.com \
--cc=buildroot@buildroot.org \
--cc=romain.naour@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.