From: Tom Rini <trini@konsulko.com>
To: Simon Glass <sjg@chromium.org>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>,
Heinrich Schuchardt <xypron.glpk@gmx.de>
Subject: Re: [PATCH v5 3/4] sandbox: Detect the host bit size automatically
Date: Thu, 3 Feb 2022 12:12:22 -0500 [thread overview]
Message-ID: <20220203171222.GW7515@bill-the-cat> (raw)
In-Reply-To: <20220123195514.3152022-4-sjg@chromium.org>
[-- Attachment #1: Type: text/plain, Size: 895 bytes --]
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@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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2022-02-03 17:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-23 19:55 [PATCH v5 0/4] Fix compiler warnings for 32-bit ARM Simon Glass
2022-01-23 19:55 ` [PATCH v5 1/4] scripts/checkpatch.pl: Resync with v5.16 Simon Glass
2022-02-04 0:40 ` Tom Rini
2022-01-23 19:55 ` [PATCH v5 2/4] efi: Use 16-bit unicode strings Simon Glass
2022-02-04 0:40 ` [PATCH v5 2/4] efi: Use 16-bit Unicode strings Tom Rini
2022-01-23 19:55 ` [PATCH v5 3/4] sandbox: Detect the host bit size automatically Simon Glass
2022-02-03 17:12 ` Tom Rini [this message]
2022-02-03 18:51 ` Heinrich Schuchardt
2022-01-23 19:55 ` [PATCH v5 4/4] treewide: Use 16-bit unicode strings Simon Glass
2022-02-03 18:56 ` Heinrich Schuchardt
2022-02-04 0:40 ` Tom Rini
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=20220203171222.GW7515@bill-the-cat \
--to=trini@konsulko.com \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.de \
/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