From: Jon Mason <jdmason@kudzu.us>
To: meta-arm@lists.yoctoproject.org, Javier Tia <javier.tia@linaro.org>
Subject: Re: [PATCH] trusted-firmware-a: fix build error when using ccache
Date: Fri, 13 Oct 2023 12:03:14 -0400 [thread overview]
Message-ID: <169721299736.1302487.7377394578893639879.b4-ty@arm.com> (raw)
In-Reply-To: <20231007223019.2557075-1-javier.tia@linaro.org>
On Sat, 07 Oct 2023 16:30:19 -0600, Javier Tia wrote:
> When ccache is enabled trusted-firmware-a recipe fails with this
> error message:
>
> make: *** No rule to make target 'aarch64-poky-linux-gcc'. Stop.
>
> ccache prefix CC variable with 'ccache' word before compiler. Because
> there are no quotes assigned to CC, only 'ccache' is assigned. The
> compiler becomes a make target, producing the build error.
>
> [...]
Applied, thanks!
[1/1] trusted-firmware-a: fix build error when using ccache
commit: f2efb2a45610216cb6c2d72bdb5d5e61b990064a
Best regards,
--
Jon Mason <jon.mason@arm.com>
prev parent reply other threads:[~2023-10-13 16:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-07 22:30 [PATCH] trusted-firmware-a: fix build error when using ccache Javier Tia
2023-10-13 16:03 ` Jon Mason [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=169721299736.1302487.7377394578893639879.b4-ty@arm.com \
--to=jdmason@kudzu.us \
--cc=javier.tia@linaro.org \
--cc=meta-arm@lists.yoctoproject.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).