From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Brandon Maier via buildroot <buildroot@buildroot.org>
Cc: Sergey Matyukevich <geomatsi@gmail.com>,
Brandon Maier <brandon.maier@collins.com>
Subject: Re: [Buildroot] [PATCH 1/1] boot/arm-trusted-firmware: enable verbose output
Date: Sun, 5 May 2024 15:39:59 +0200 [thread overview]
Message-ID: <20240505153959.14f8ef6b@windsurf> (raw)
In-Reply-To: <20240412211222.26585-1-brandon.maier@collins.com>
On Fri, 12 Apr 2024 21:12:22 +0000
Brandon Maier via buildroot <buildroot@buildroot.org> wrote:
> Signed-off-by: Brandon Maier <brandon.maier@collins.com>
> ---
> boot/arm-trusted-firmware/arm-trusted-firmware.mk | 1 +
> 1 file changed, 1 insertion(+)
I am confused as to why this patch is needed: for both Linux and
U-Boot, we don't need to do anything special, just doing "make V=1" at
the top-level, the V=1 gets passed down to Linux/U-Boot, and they
exhibit a verbose build. However, that doesn't work with
arm-trusted-firmware indeed, so I have applied your patch which makes
the build verbose also for arm-trusted-firmware. Still a bit unclear as
to why it doesn't work "by default".
Best regards,
Thomas
--
Thomas Petazzoni, CTO, 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:[~2024-05-05 13:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 21:12 [Buildroot] [PATCH 1/1] boot/arm-trusted-firmware: enable verbose output Brandon Maier via buildroot
2024-05-05 13:39 ` Thomas Petazzoni via buildroot [this message]
2024-05-06 18:15 ` [Buildroot] [External] " Maier, Brandon L Collins via buildroot
2024-05-06 18:52 ` Thomas Petazzoni via buildroot
2024-05-22 6:12 ` [Buildroot] " Peter Korsgaard
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=20240505153959.14f8ef6b@windsurf \
--to=buildroot@buildroot.org \
--cc=brandon.maier@collins.com \
--cc=geomatsi@gmail.com \
--cc=thomas.petazzoni@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.