On Sun, Jan 23, 2022 at 12:55:13PM -0700, Simon Glass wrote: > At present if you build sandbox on a 32-bit host a lot of errors are > produced. This is because CONFIG_HOST_64BIT is enabled by default. > > It is quite annoying to have to change that manually before building > sandbox. It is also quite confusing for new users. > > Add a way to detect the setting and add the appropriate > CONFIG_HOST_64BIT=y or CONFIG_HOST_32BIT=y to the defconfig, to avoid > this issue. > > Tidy up the Kconfig help for the above two options while we are here. > > Signed-off-by: Simon Glass <s...@chromium.org>
This pretty reliably fails to build for me with CONFIG_HOST_DETECT_BITNESS=y resulting in CONFIG_SANDBOX_BITS_PER_LONG not being set. It's as easy to trigger as "make O=/tmp/fail sandbox_config all" for me (over on bill-the-cat if it works for you locally). -- Tom
signature.asc
Description: PGP signature
