From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: peter.kjellerstedt@axis.com, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 2/2] busybox: Remove CONFIG_SHA1_SMALL and CONFIG_SHA*_HWACCEL from sha*sum.cfg
Date: Wed, 26 Aug 2026 09:47:06 +0100 [thread overview]
Message-ID: <0d45bdfd177049f5e36dd8563dc32688c2c1e53e.camel@linuxfoundation.org> (raw)
In-Reply-To: <20260825191708.3014535-2-pkj@axis.com>
On Tue, 2026-08-25 at 21:17 +0200, Peter Kjellerstedt via lists.openembedded.org wrote:
> The options CONFIG_SHA1_SMALL, CONFIG_SHA1_HWACCEL and
> CONFIG_SHA256_HWACCEL affect the common implementations of SHA-1 and
> SHA-256. These are used regardless of if the sha1sum and/or sha256sum
> applets are enabled. Thus it does not make sense to configure them in
> the sha*sum.cfg files. Additionally, their values in the .cfg files
> match the values in the defconfig file.
Something in this series seems to be causing:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/19/builds/4483
stdio: ERROR: busybox-1.38.0-r0 do_package_qa: QA Issue: busybox: ELF binary /bin/busybox.nosuid has relocations in .text [textrel]
stdio: ERROR: busybox-1.38.0-r0 do_package_qa: Fatal QA errors were found, failing task.
:(
Cheers,
Richard
prev parent reply other threads:[~2026-08-26 8:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-25 19:17 [PATCH 1/2] Revert "busybox: Make provisions to disable sha256/sha1 accelaration on x86" Peter Kjellerstedt
2026-08-25 19:17 ` [PATCH 2/2] busybox: Remove CONFIG_SHA1_SMALL and CONFIG_SHA*_HWACCEL from sha*sum.cfg Peter Kjellerstedt
2026-08-26 8:47 ` Richard Purdie [this message]
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=0d45bdfd177049f5e36dd8563dc32688c2c1e53e.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=peter.kjellerstedt@axis.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