From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Andrej Valek <andrej.v@skyrain.eu>
Cc: Ross.Burton@arm.com, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core][PATCH v3] busybox: 1.36.1 -> 1.37.0
Date: Wed, 23 Oct 2024 16:38:17 +0100 [thread overview]
Message-ID: <0be330e10f6ac9dc2b18e284e674f201506a9fc6.camel@linuxfoundation.org> (raw)
In-Reply-To: <58fc2ed7-17d8-486e-9b0e-d4bf8588e542@skyrain.eu>
On Wed, 2024-10-23 at 17:09 +0200, Andrej Valek wrote:
> Ah, I see some errors there, but it's little bit interesting, while I
> was testing it on "core-image-sato" with:
>
> BB_VERSION = "2.9.1"
> BUILD_SYS = "x86_64-linux"
> NATIVELSBSTRING = "universal"
> TARGET_SYS = "x86_64-poky-linux"
> MACHINE = "qemux86-64"
> DISTRO = "poky"
> DISTRO_VERSION = "5.1"
> TUNE_FEATURES = "m64 core2"
>
>
> So I will test it with "poky-altcfg" and "core-image-sato-sdk" and
> hopefully hit the problem.
Looking at the pattern emerging in the failures, that looks like a good
plan!
core-image-full-cmdline looks affected and is slightly smaller too
FWIW.
Cheers,
Richard
next prev parent reply other threads:[~2024-10-23 15:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 9:48 [OE-core][PATCH] busybox: 1.36.1 -> 1.37.0 Andrej Valek
2024-10-11 12:33 ` Richard Purdie
2024-10-15 12:20 ` Andrej Valek
2024-10-18 13:48 ` Andrej Valek
2024-10-18 16:25 ` Ross Burton
2024-10-16 8:30 ` [OE-core][PATCH v2] " Andrej Valek
2024-10-19 16:02 ` [OE-core][PATCH v3] " Andrej Valek
2024-10-19 16:19 ` Patchtest results for " patchtest
2024-10-20 6:31 ` Andrej Valek
2024-10-23 9:14 ` Andrej Valek
2024-10-23 14:52 ` Richard Purdie
2024-10-23 15:09 ` Andrej Valek
2024-10-23 15:38 ` Richard Purdie [this message]
2024-10-23 17:24 ` Andrej Valek
2024-10-23 17:22 ` [OE-core][PATCH v4] " Andrej Valek
2024-10-23 17:33 ` Patchtest results for " patchtest
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=0be330e10f6ac9dc2b18e284e674f201506a9fc6.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=Ross.Burton@arm.com \
--cc=andrej.v@skyrain.eu \
--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