Re: git: 1dfcff294e44 - main - release: increase IMAGE_SIZE for arm, arm64, riscv

On Thu, Jul 14, 2022 at 08:10:12AM -0700, Mark Millard wrote:
[... snip ...]

> But it does not appear that modern /usr/src/release/ by itself
> would produce the inefficient alignments unless the mdconfig
> and gpart combination used did something odd overall that
> did not happen in my example sequence.
> 
> Here, I'm just using the mismatch to indicate that the snapshot
> and release builds do not seem to match what /usr/src/release/
> is set up to do. I've not managed to reproduce the alignment
> that the snapshot and release .img files have in them by
> following the /usr/src/release steps for the example Small
> Board Computer that I'm using to illustrate the issue.
> 
> It suggests something odd is going on for the official image
> builds that makes the difference. What, I've no clue.
> 

I do not know either, but I have been looking into it.  All of the
userland utilities (mkimg, makefs, etc) that are used are used *within*
the build chroot, so I see no sign of any "leakage" from the build host
itself creeping into the process.

Additionally, I double-checked (and triple-checked) the configuration
files used for these builds, and there are no stale artifacts of
overriding IMAGE_SIZE or any other variables - everything sources the
in-tree ${srcdir}/release/${TARGET}/${TARGET_ARCH}.conf (i.e.,
release/riscv/riscv64.conf, for example).

That said, there have been a few updates to PR 264032 overnight that has
lead to some head-scratching.

By the way, thank you for poking into this in the depth that you had.
It is very much appreciated.

Glen