From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH v2] libgcc: Bump PR/HASHEQUIV_HASH_VERSION after reproducibility issues
Date: Thu, 9 Apr 2026 21:16:51 +0100 [thread overview]
Message-ID: <20260409201651.3485286-1-richard.purdie@linuxfoundation.org> (raw)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
meta/recipes-devtools/gcc/libgcc_15.2.bb | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/meta/recipes-devtools/gcc/libgcc_15.2.bb b/meta/recipes-devtools/gcc/libgcc_15.2.bb
index fdcd6cc0da1..59c70ea4323 100644
--- a/meta/recipes-devtools/gcc/libgcc_15.2.bb
+++ b/meta/recipes-devtools/gcc/libgcc_15.2.bb
@@ -5,3 +5,7 @@ LDFLAGS += "-fuse-ld=bfd"
# Building with thumb enabled on armv6t fails
ARM_INSTRUCTION_SET:armv6 = "arm"
+
+# remove at next version upgrade or when output changes
+PR = "r1"
+HASHEQUIV_HASH_VERSION .= ".1"
next reply other threads:[~2026-04-09 20:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 20:16 Richard Purdie [this message]
2026-04-09 20:30 ` Patchtest results for [PATCH v2] libgcc: Bump PR/HASHEQUIV_HASH_VERSION after reproducibility issues patchtest
-- strict thread matches above, loose matches on Subject: below --
2026-04-09 21:52 Richard Purdie
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=20260409201651.3485286-1-richard.purdie@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox