From: Tom Rini <trini@konsulko.com>
To: "Jacky.Cao@sony.com" <Jacky.Cao@sony.com>
Cc: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>,
"u-boot@lists.denx.de" <u-boot@lists.denx.de>,
"nora.schiffer@ew.tq-group.com" <nora.schiffer@ew.tq-group.com>,
"Steffen.Doster@tq-group.com" <Steffen.Doster@tq-group.com>,
"alexander.feilke@ew.tq-group.com"
<alexander.feilke@ew.tq-group.com>,
"Max.Merchel@ew.tq-group.com" <Max.Merchel@ew.tq-group.com>
Subject: Re: [PATCH v1] env: Fix compile error for envtools
Date: Tue, 14 Jul 2026 15:38:02 -0600 [thread overview]
Message-ID: <20260714213802.GF749385@bill-the-cat> (raw)
In-Reply-To: <KL1PR04MB6734A43A5179C30DA1F9B9A887F92@KL1PR04MB6734.apcprd04.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 736 bytes --]
On Tue, Jul 14, 2026 at 03:04:42AM +0000, Jacky.Cao@sony.com wrote:
> > > I use master branch of OSS u-boot repo and meet the issue with below
> > > commands:
> > >
> > > make mx6qsabrelite_defconfig
> > > make -j8
> > > make tools envtools
> >
> > What host distribution are you building on? And, <config.h> *must* come first
> > in the include list, for it to function correctly.
>
> Host OS is Ubuntu 22.04.3 LTS.
> Toolchain is Arm GNU Toolchain 11.3.Rel1(arm-none-linux-gnueabihf-).
> Also tried Ubuntu 24.04.4 LTS and Arm GNU Toolchain 15.3.Rel1,
> the issue still happens.
So, are you on an ARM host too? You aren't specifying where you are /
aren't using the ARM toolchain in the above. Thanks.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-07-14 21:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-13 8:31 [PATCH v1] env: Fix compile error for envtools Jacky Cao
2026-07-13 10:31 ` Peng Fan (OSS)
2026-07-14 1:35 ` Jacky.Cao
2026-07-14 1:53 ` Tom Rini
2026-07-14 3:04 ` Jacky.Cao
2026-07-14 21:38 ` Tom Rini [this message]
2026-07-15 5:02 ` Jacky.Cao
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=20260714213802.GF749385@bill-the-cat \
--to=trini@konsulko.com \
--cc=Jacky.Cao@sony.com \
--cc=Max.Merchel@ew.tq-group.com \
--cc=Steffen.Doster@tq-group.com \
--cc=alexander.feilke@ew.tq-group.com \
--cc=nora.schiffer@ew.tq-group.com \
--cc=peng.fan@oss.nxp.com \
--cc=u-boot@lists.denx.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