From: Luca Ceresoli via buildroot <buildroot@buildroot.org>
To: Neal Frager <neal.frager@amd.com>
Cc: yann.morin@orange.com, ibai.erkiaga-elorza@amd.com,
buildroot@buildroot.org, brandon.maier@collins.com, ju.o@free.fr,
thomas.petazzoni@bootlin.com, romain.naour@smile.fr,
michal.simek@amd.com, romain.naour@gmail.com
Subject: Re: [Buildroot] [PATCH v2 1/1] boot/arm-trusted-firmware: override BL31 environment variable error
Date: Wed, 10 Sep 2025 10:11:17 +0200 [thread overview]
Message-ID: <20250910101118.3bb72b85@booty> (raw)
In-Reply-To: <20250905122603.2521801-1-neal.frager@amd.com>
Hello Neal,
On Fri, 5 Sep 2025 13:26:03 +0100
Neal Frager <neal.frager@amd.com> wrote:
> When building the arm-trusted-firmware, if the host environment has a value
> configured in the BL31 variable such as the following:
>
> export BL31=/tmp/bl31.elf
>
> This will cause the build of the bl31.elf to be skipped leading to the
> following build error:
>
> make[1]: Nothing to be done for 'bl31'.
> And then:
> readelf: Error: './output/build/arm-trusted-firmware-custom/build/versal/release/bl31/bl31.elf': No such file
>
> To fix this, clear the BL31 variable in the MAKE_OPTS, so that building the
> arm-trusted-firmware will build regardless of the host environment.
>
> Signed-off-by: Neal Frager <neal.frager@amd.com>
Nice bug!
Tested-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
I'm not sure whether this is the correct solution or rather we should
unexport BL31 in the main Makefile (in the "Hide troublesome environment
variables from sub processes" section). However as far as I can say
this is OK, and definitely self-contained since it's likely that other
packages won't be affected by a BL31 host environment variable, so:
Reviewed-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Luca
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-09-10 8:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-05 12:26 [Buildroot] [PATCH v2 1/1] boot/arm-trusted-firmware: override BL31 environment variable error Neal Frager via buildroot
2025-09-10 8:11 ` Luca Ceresoli via buildroot [this message]
2025-09-10 9:44 ` Frager, Neal via buildroot
2026-01-02 17:27 ` Thomas Petazzoni via buildroot
2026-01-13 19:45 ` Arnout Vandecappelle via buildroot
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=20250910101118.3bb72b85@booty \
--to=buildroot@buildroot.org \
--cc=brandon.maier@collins.com \
--cc=ibai.erkiaga-elorza@amd.com \
--cc=ju.o@free.fr \
--cc=luca.ceresoli@bootlin.com \
--cc=michal.simek@amd.com \
--cc=neal.frager@amd.com \
--cc=romain.naour@gmail.com \
--cc=romain.naour@smile.fr \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin@orange.com \
/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