Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Dora, Sunil Kumar" <SunilKumar.Dora@windriver.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/8] erofs-utils: Make reproducible for different BUILD_ARCH
Date: Mon, 28 Sep 2026 04:47:25 -0700	[thread overview]
Message-ID: <1008103.1790596045910735679@lists.openembedded.org> (raw)
In-Reply-To: <20260927164631.2484854-1-richard.purdie@linuxfoundation.org>

[-- Attachment #1: Type: text/plain, Size: 617 bytes --]

I might be missing something, but I think the aarch64 case can still leak.
In configure.ac, right after the cached sysconf check there's:

AS_CASE([$build_cpu], [aarch64*], ... erofs_cv_max_block_size=16384 ...)

so on an aarch64 worker building qemux86-64 the cached 4096 still gets bumped to 16384.
When I tried the v1.9.4 configure with --build=aarch64-linux --host=x86_64-linux, config.h ended up with 16384.

Passing MAX_BLOCK_SIZE=${BLOCKSIZE} instead seems to skip that whole block.
The next 119 run should show it, as long as reproducibleA picks up erofs-utils from x86_64 sstate.

Thanks,
Sunil

[-- Attachment #2: Type: text/html, Size: 686 bytes --]

  parent reply	other threads:[~2026-09-28 11:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-27 16:46 [PATCH 1/8] erofs-utils: Make reproducible for different BUILD_ARCH Richard Purdie
2026-09-27 16:46 ` [PATCH 2/8] diffoscope: upgrade 330 -> 331 Richard Purdie
2026-09-27 16:46 ` [PATCH 3/8] python3-markdown: upgrade 3.10.3 -> 3.11 Richard Purdie
2026-09-27 16:46 ` [PATCH 4/8] epiphany: upgrade 51.0 -> 51.1 Richard Purdie
2026-09-27 16:46 ` [PATCH 5/8] libpam: upgrade 1.7.2 -> 1.7.3 Richard Purdie
2026-09-27 16:46 ` [PATCH 6/8] libuv: upgrade 1.52.1 -> 1.53.0 Richard Purdie
2026-09-27 16:46 ` [PATCH 7/8] parted: upgrade 3.7 -> 3.8 Richard Purdie
2026-09-27 16:46 ` [PATCH 8/8] python3-uv-build: upgrade 0.12.17 -> 0.12.19 Richard Purdie
2026-09-28 11:47 ` Dora, Sunil Kumar [this message]
2026-09-28 13:13   ` [OE-core] [PATCH 1/8] erofs-utils: Make reproducible for different BUILD_ARCH 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=1008103.1790596045910735679@lists.openembedded.org \
    --to=sunilkumar.dora@windriver.com \
    --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