From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Gavin Schenk <g.schenk@eckelmann.de>
Subject: Re: [ptxdist] [APPLIED] host-tf-a: Disable compiler autodetection
Date: Mon, 22 Jun 2026 10:11:29 +0200 [thread overview]
Message-ID: <20260622081129.3426127-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20260603051117.3969413-1-g.schenk@eckelmann.de>
Thanks, applied as f863d8a8e234fcf93593721bdaa1324ee76928ff.
Michael
[sent from post-receive hook]
On Mon, 22 Jun 2026 10:11:29 +0200, Gavin Schenk <g.schenk@eckelmann.de> wrote:
> On recent gnu make version compiler autodetection fails.
>
> Michael stated in IRC:
>
> It's a whitespace issue. If the tool is not found, then in
> make_helpers/toolchain.mk toolchain-warn-unrecognized is called and that
> expands to multiple empty lines, so $1-$2-id contains those and that
> breaks somewhere later.
>
> Setting CC=gcc is a good solution. It overwrites the autodetection. And
> since we don't use it anyways, because we just build fiptool (which uses
> HOSTCC), it does not really matter what we set there
>
> Signed-off-by: Gavin Schenk <g.schenk@eckelmann.de>
> Message-Id: <20260603051117.3969413-1-g.schenk@eckelmann.de>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/host-tf-a.make b/rules/host-tf-a.make
> index 38f0006428e1..aff89dae58e1 100644
> --- a/rules/host-tf-a.make
> +++ b/rules/host-tf-a.make
> @@ -10,7 +10,7 @@
> #
> HOST_PACKAGES-$(PTXCONF_HOST_TF_A) += host-tf-a
>
> -HOST_TF_A_MAKE_OPT = fiptool
> +HOST_TF_A_MAKE_OPT = fiptool CC=gcc
>
> $(STATEDIR)/host-tf-a.install:
> @$(call targetinfo)
prev parent reply other threads:[~2026-06-22 8:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 5:10 [ptxdist] [PATCH] " Gavin Schenk
2026-06-22 8:11 ` Michael Olbrich [this message]
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=20260622081129.3426127-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=g.schenk@eckelmann.de \
--cc=ptxdist@pengutronix.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