[PATCH v5 3/4] sandbox: Detect the host bit size automatically
Tom Rini
trini at konsulko.com
Thu Feb 3 18:12:22 CET 2022
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 <sjg at 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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20220203/9c46c605/attachment.sig>
More information about the U-Boot
mailing list