From: Giulio Benetti <giulio.benetti@benettiengineering.com>
To: buildroot@buildroot.org
Cc: Giulio Benetti <giulio.benetti@benettiengineering.com>,
Matt Weber <matthew.weber@collins.com>
Subject: [Buildroot] [PATCH] package/ace: fix build failure due to gcc bug 101915
Date: Sun, 14 Aug 2022 05:32:53 +0200 [thread overview]
Message-ID: <20220814033253.575354-1-giulio.benetti@benettiengineering.com> (raw)
The ace package exhibits gcc bug 101915 when built for the Microblaze
architecture with optimization enabled, which causes a build failure.
As done for other packages in Buildroot work around this gcc bug by
setting optimization to -O0 if BR2_TOOLCHAIN_HAS_GCC_BUG_101915=y.
Fixes:
http://autobuild.buildroot.net/results/f8f/f8f8de99abe92175954c370ad99fee43942bcdcc/
Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
---
package/ace/ace.mk | 11 ++++++++++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/package/ace/ace.mk b/package/ace/ace.mk
index 7299f0d40c..6f381d5da5 100644
--- a/package/ace/ace.mk
+++ b/package/ace/ace.mk
@@ -17,9 +17,18 @@ ACE_CPE_ID_PRODUCT = adaptive_communication_environment
# Only compiling ACE libraries (no TAO)
ACE_LIBARIES = ace ACEXML Kokyu netsvcs protocols/ace
+ACE_CPPFLAGS = $(TARGET_CPPFLAGS)
+
+ifeq ($(BR2_TOOLCHAIN_HAS_GCC_BUG_101915),y)
+ACE_CPPFLAGS += -O0
+endif
+
+# ace requires -std=c++11
+ACE_CPPFLAGS += -std=c++11
+
ACE_MAKE_OPTS = \
ACE_ROOT="$(@D)" \
- DEFFLAGS="$(TARGET_CPPFLAGS) -std=c++11"
+ DEFFLAGS="$(ACE_CPPFLAGS)"
ifeq ($(BR2_PACKAGE_OPENSSL),y)
ACE_LIBARIES += ace/SSL
--
2.34.1
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2022-08-14 3:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-14 3:32 Giulio Benetti [this message]
2022-08-14 13:33 ` [Buildroot] [PATCH] package/ace: fix build failure due to gcc bug 101915 Yann E. MORIN
2022-09-15 9:46 ` Peter Korsgaard
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=20220814033253.575354-1-giulio.benetti@benettiengineering.com \
--to=giulio.benetti@benettiengineering.com \
--cc=buildroot@buildroot.org \
--cc=matthew.weber@collins.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox