Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Alexis Lothoré via buildroot" <buildroot@buildroot.org>
To: "Baruch Siach" <baruch@tkos.co.il>,
	"Thomas Perale via buildroot" <buildroot@buildroot.org>
Cc: "Romain Naour" <romain.naour@smile.fr>,
	"Thomas Perale" <thomas.perale@mind.be>
Subject: Re: [Buildroot] [PATCH 2/2] package/iozone: Fix parallel build problem
Date: Fri, 31 Oct 2025 10:50:10 +0100	[thread overview]
Message-ID: <DDWEX0A8U40C.1J7DHEPBK82OY@bootlin.com> (raw)
In-Reply-To: <87ldmjesxl.fsf@tarshish>

Hello,

On Fri Sep 12, 2025 at 2:50 PM CEST, Baruch Siach via buildroot wrote:
> Hi Thomas,
>
> On Thu, Sep 11 2025, Thomas Perale via buildroot wrote:
>> In reply of:
>>> Apply a patch from meta-openembedded fixing a cross-build issue [1].
>>> 
>>> [1]
>>> https://github.com/openembedded/meta-openembedded/blob/walnascar/meta-oe/recipes-benchmark/iozone3/iozone3/parallelism.patch
>>> 
>>> Fixes:
>>> https://gitlab.com/buildroot.org/buildroot/-/jobs/11176774405 (TestIozone)
>>> 
>>> Signed-off-by: Romain Naour <romain.naour@smile.fr>
>>
>> Applied to 2025.02.x & 2025.05.x. Thanks
>
> Not in 2025.02.x or 2025.05.x as of a4ac42f4e7a74 ("Revert
> "package/firewalld: add missing nftables json runtime dependency"") and
> 02f4d62bbf95 ("package/python3: do build-time detection of non-working
> toolchain"), respectively.

I was investigating a build failure on the iozone package on buildroot
2025.02.x, and eventually found this series which indeed fixes the issues
observed locally. As Baruch stated, it does not seem to be applied on
2025.02.x, despite Thomas's notification.

Any plan to eventually apply it on 2025.02.x ?

Thanks,

Alexis

-- 
Alexis Lothoré, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2025-10-31  9:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-06 16:25 [Buildroot] [PATCH 1/2] package/iozone: bump to version 3.508 Romain Naour via buildroot
2025-09-06 16:25 ` [Buildroot] [PATCH 2/2] package/iozone: Fix parallel build problem Romain Naour via buildroot
2025-09-11 19:26   ` Thomas Perale via buildroot
2025-09-12 12:50     ` Baruch Siach via buildroot
2025-10-31  9:50       ` Alexis Lothoré via buildroot [this message]
2025-10-31 15:00         ` Thomas Perale via buildroot
2025-10-31 15:39           ` Alexis Lothoré via buildroot
2025-11-01 18:03             ` Thomas Perale via buildroot
2025-11-17 19:51     ` Arnout Vandecappelle via buildroot
2025-09-06 17:03 ` [Buildroot] [PATCH 1/2] package/iozone: bump to version 3.508 Julien Olivain via buildroot

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=DDWEX0A8U40C.1J7DHEPBK82OY@bootlin.com \
    --to=buildroot@buildroot.org \
    --cc=alexis.lothore@bootlin.com \
    --cc=baruch@tkos.co.il \
    --cc=romain.naour@smile.fr \
    --cc=thomas.perale@mind.be \
    /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