Date: Thu, 14 Jul 2022 15:21:25 +0000 From: Glen Barber <gjb@freebsd.org> To: Mark Millard <marklmi@yahoo.com> Cc: dev-commits-src-main@freebsd.org Subject: Re: git: 1dfcff294e44 - main - release: increase IMAGE_SIZE for arm, arm64, riscv Message-ID: <20220714152125.GB30607@FreeBSD.org> In-Reply-To: <4D903E5A-58FB-4516-AC53-AEDFF48564A7@yahoo.com> References: <84410D65-6F86-44E5-8B14-8A523C9919C7.ref@yahoo.com> <84410D65-6F86-44E5-8B14-8A523C9919C7@yahoo.com> <20220713201327.GY30607@FreeBSD.org> <7F4F9683-B4DE-4F65-BBD7-027039A0C270@yahoo.com> <20220713204227.GA30607@FreeBSD.org> <8A02A4A4-9F3A-47F2-9985-EA2151043BB7@yahoo.com> <4D903E5A-58FB-4516-AC53-AEDFF48564A7@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--wGJqb8EFafMIlOCd
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
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.
>=20
> 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.
>=20
> It suggests something odd is going on for the official image
> builds that makes the difference. What, I've no clue.
>=20
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
--wGJqb8EFafMIlOCd
Content-Type: application/pgp-signature; name="signature.asc"
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEjRJAPC5sqwhs9k2jAxRYpUeP4pMFAmLQNHAACgkQAxRYpUeP
4pOtrA/+Ky3DaFAqaj9xIby2mr94qkzwc58z/Z7hxlQbglOOosKKdM1qLc3h1Qgr
rkmN+tS2lAwxmNOXCtuTscYtyQTKsXCx88izqjk4WLv6yG2xa3HKyt/yKMi+ORKP
XcaHkZ+M2/jsUsunOSilBkJMlgrV/Egmdi48WCCC8nchmSOMgfIDdxtYZ/7G91S9
lNaSrn6NIPZbfGZT/8xL5ZuzVZNTZ8AODoYCcklClMY8e8HDRg5v7E/OhMh6bUiV
IWlPVY2KzxNzRScq5+dhEYMTJiECJjzeQadwCDPXVjHD4mDkq4LusO55ZNuvYwKI
3Daj8tGfJ+YlrlBa2aLIX/MlUvzMR0AE8/Qfkkj1WIKx4l82k0pxbyU7KIJ2xuQO
zKngn6dwn3euTDk6/j61m9y6DTXZWGxNs5iLzCZhdnTSK77rBewxMXl/sZkwg9a2
sptXqkUfMOM74f6KzWY2jFOpD6aHRpleAbYNlgLj+XoFG68sQJpHEAvKnGuwM7RZ
ph6jwWkkeXkiuAr0TIK6ufr1ZczpT4JPnaXLI/Tmxl9UXkrfc9ERiWVPTksTwENK
OyhCSDYhJtuQR2mos/R08dnHj2dGk5ipKBk2zee6+U5skGrblbdSGWKuN1E+6L3f
3LmD8N17jxta24VposF2GDPJB3UfHWBXCJE06E7qgmHN0NQovFQ=
=RS7E
-----END PGP SIGNATURE-----
--wGJqb8EFafMIlOCd--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20220714152125.GB30607>