From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: raj.khem@gmail.com, openembedded-core@lists.openembedded.org
Cc: Khem Raj <khem.raj@oss.qualcomm.com>
Subject: Re: [OE-core] [PATCH 3/4] strace: Fix build with std=gnu23
Date: Tue, 14 Apr 2026 07:23:19 +0100 [thread overview]
Message-ID: <31246c7aabc2eccb237f4c5b2e36e91184fe5314.camel@linuxfoundation.org> (raw)
In-Reply-To: <20260411002929.571805-3-khem.raj@oss.qualcomm.com>
On Fri, 2026-04-10 at 17:29 -0700, Khem Raj via lists.openembedded.org wrote:
> This does not build on hosts with gcc <= 13 which does not have std=gnu23
> dialect option e.g. ubuntu 24.04, especially with clang which does not
> default to gnu23 yet like gcc-15, so autoconf 2.73 decided to enforce the
> standard with clang which then spills into CC_FOR_BUILD as well without
> this patch
>
> Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
> ---
> ...kport-ax_prog_cc_for_build.m4-macros.patch | 229 ++++++++++++++++++
> meta/recipes-devtools/strace/strace_6.19.bb | 1 +
> 2 files changed, 230 insertions(+)
> create mode 100644 meta/recipes-devtools/strace/strace/0001-m4-Backport-ax_prog_cc_for_build.m4-macros.patch
We have the same issue in strace's ptest Makefile as we did with apr:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/37/builds/3822
which leads to:
https://valkyrie.yocto.io/pub/repro-fail/oe-reproducible-20260413-8huodsh5/packages/diff-html/
CC_FOR_BUILD = gcc -std=gnu23
vs
CC_FOR_BUILD = gcc
so we probably need a similar sed fix there?
Cheers,
Richard
next prev parent reply other threads:[~2026-04-14 6:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-11 0:29 [PATCH 1/4] sudo: Fix build with std=gnu23 Khem Raj
2026-04-11 0:29 ` [PATCH 2/4] bind: " Khem Raj
2026-04-11 0:29 ` [PATCH 3/4] strace: " Khem Raj
2026-04-14 6:23 ` Richard Purdie [this message]
2026-04-11 0:29 ` [PATCH 4/4] vulkan-samples: Upgrade to latest tip of trunk Khem Raj
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=31246c7aabc2eccb237f4c5b2e36e91184fe5314.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=khem.raj@oss.qualcomm.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox