All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hemanth.KumarMD@windriver.com
To: openembedded-core@lists.openembedded.org
Cc: Sundeep.Kokkonda@windriver.com, Randy.MacLeod@windriver.com,
	Hemanth.KumarMD@windriver.com
Subject: [PATCH v3 3/6] gcc-runtime: avoid discarded-qualifiers build failure with glibc 2.43
Date: Tue, 10 Mar 2026 10:44:00 -0700	[thread overview]
Message-ID: <20260310174403.2309825-3-Hemanth.KumarMD@windriver.com> (raw)
In-Reply-To: <20260310174403.2309825-1-Hemanth.KumarMD@windriver.com>

From: Hemanth Kumar M D <Hemanth.KumarMD@windriver.com>

With the glibc 2.43 upgrade, building gcc-runtime triggers a
-Wdiscarded-qualifiers warning in libgomp/affinity-fmt.c which
becomes a build failure due to -Werror.

Add -Wno-error=discarded-qualifiers to CFLAGS as a workaround until
the upstream const-correctness issue in libgomp is resolved.

Signed-off-by: Hemanth Kumar M D <Hemanth.KumarMD@windriver.com>
---
 meta/recipes-devtools/gcc/gcc-runtime.inc | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-devtools/gcc/gcc-runtime.inc b/meta/recipes-devtools/gcc/gcc-runtime.inc
index c4e1c5b9a5..ef38cff58a 100644
--- a/meta/recipes-devtools/gcc/gcc-runtime.inc
+++ b/meta/recipes-devtools/gcc/gcc-runtime.inc
@@ -7,7 +7,8 @@ SUMMARY = "Runtime libraries from GCC"
 LICENSE = "GPL-3.0-with-GCC-exception"
 
 CXXFLAGS:remove = "-fvisibility-inlines-hidden"
-
+CFLAGS:append = " -Wno-error=discarded-qualifiers"
+ 
 EXTRA_OECONF_PATHS = "\
     --with-gxx-include-dir=${includedir}/c++/${BINV} \
     --with-sysroot=/not/exist \
-- 
2.49.0



  parent reply	other threads:[~2026-03-10 17:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-10 17:43 [PATCH v3 1/6] glibc: Upgrade to 2.43 release Hemanth.KumarMD
2026-03-10 17:43 ` [PATCH v3 2/6] gettext: upgrade 0.26 -> 1.0 Hemanth.KumarMD
2026-03-10 17:44 ` Hemanth.KumarMD [this message]
2026-03-10 17:44 ` [PATCH v3 4/6] libxcrypt: avoid discarded-qualifiers build failure with glibc 2.43 Hemanth.KumarMD
2026-03-10 17:44 ` [PATCH v3 5/6] barebox-tools: fix " Hemanth.KumarMD
2026-03-10 18:06   ` [OE-core] " Alexander Kanavin
2026-03-12 19:07     ` Randy MacLeod
2026-03-12 19:17       ` Alexander Kanavin
2026-03-13 17:15         ` Ahmad Fatoum
2026-03-17 10:14           ` Hemanth Kumar M D
2026-03-17 12:14             ` Alexander Kanavin
2026-03-10 17:44 ` [PATCH v3 6/6] ltp: workaround openat2 " Hemanth.KumarMD
2026-03-10 18:05   ` [OE-core] " Alexander Kanavin
2026-03-11 13:43 ` [OE-core] [PATCH v3 1/6] glibc: Upgrade to 2.43 release Mathieu Dubois-Briand
2026-03-11 17:43   ` Mathieu Dubois-Briand

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=20260310174403.2309825-3-Hemanth.KumarMD@windriver.com \
    --to=hemanth.kumarmd@windriver.com \
    --cc=Randy.MacLeod@windriver.com \
    --cc=Sundeep.Kokkonda@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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.