From: Jon Mason <jdmason@kudzu.us>
To: Adrian DC <radian.dc@gmail.com>
Cc: meta-arm@lists.yoctoproject.org,
Javier Tia <javier.tia@linaro.org>, Jon Mason <jon.mason@arm.com>
Subject: Re: [PATCH] trusted-firmware-a: fix build error when using ccache
Date: Mon, 30 Sep 2024 10:00:54 -0400 [thread overview]
Message-ID: <ZvqvFhYoRXQ9RQ4H@kudzu.us> (raw)
In-Reply-To: <20240928155436.1145975-1-radian.dc@gmail.com>
On Sat, Sep 28, 2024 at 05:54:36PM +0200, Adrian DC wrote:
> From: Javier Tia <javier.tia@linaro.org>
>
> 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.
>
> Add single quotes to LD is a good measure to prevent this kind of error.
>
> Signed-off-by: Javier Tia <javier.tia@linaro.org>
> Signed-off-by: Jon Mason <jon.mason@arm.com>
> Signed-off-by: Adrian DC <radian.dc@gmail.com>
I have questions about this patch's origins, given the above s-o-b's.
Signed-off-by's state an authorship or handling (see Developer’s
Certificate of Origin). Since I have not seen this patch, I should
not be listed. It's on me to add my s-o-b. Also, the ordering tends
to matter, as each person handling the patch adds their s-o-b at the
end of the patch. So, you should be second, since you are taking this
from Javier and submitting it for him (nd I would be last since
I'mtaking it from you).
Also, this feels like it needs a "Fixes:" line. So, I know how far to
pull this back in the stable branches.
Finally, I find it weird that Javier isn't submitting this himself.
Javier appears to be the author, and it includes his Linaro emaila
ddress, and you are sending it from a gmail account. Are you
co-authors? Are you sending it with his approval because he is
busy/vacationing/ill?
Overall the patch is fine and I would normally include it, but this is
weird to me. If Javier acks it to confirm his authoer, then I'll move
my s-o-b to the end and include it.
Thanks,
Jon
> ---
> .../recipes-bsp/trusted-firmware-a/trusted-firmware-a.inc | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/meta-arm/recipes-bsp/trusted-firmware-a/trusted-firmware-a.inc b/meta-arm/recipes-bsp/trusted-firmware-a/trusted-firmware-a.inc
> index 2e3b50c5..5d3da59b 100644
> --- a/meta-arm/recipes-bsp/trusted-firmware-a/trusted-firmware-a.inc
> +++ b/meta-arm/recipes-bsp/trusted-firmware-a/trusted-firmware-a.inc
> @@ -101,9 +101,9 @@ def remove_options_tail (in_string):
> from itertools import takewhile
> return ' '.join(takewhile(lambda x: not x.startswith('-'), in_string.split(' ')))
>
> -EXTRA_OEMAKE += "LD=${@remove_options_tail(d.getVar('LD'))}"
> +EXTRA_OEMAKE += "LD='${@remove_options_tail(d.getVar('LD'))}'"
>
> -EXTRA_OEMAKE += "CC=${@remove_options_tail(d.getVar('CC'))}"
> +EXTRA_OEMAKE += "CC='${@remove_options_tail(d.getVar('CC'))}'"
>
> # Verbose builds, no -Werror
> EXTRA_OEMAKE += "V=1 E=0"
> --
> 2.43.0
>
>
next prev parent reply other threads:[~2024-09-30 14:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-28 15:54 [PATCH] trusted-firmware-a: fix build error when using ccache Adrian DC
2024-09-30 14:00 ` Jon Mason [this message]
2024-09-30 22:47 ` Javier Tia
2024-09-30 23:02 ` Jon Mason
2024-10-01 1:56 ` Adrian DC
2024-10-01 16:10 ` [meta-arm] " Denys Dmytriyenko
2024-10-02 13:07 ` Jon Mason
2024-10-06 10:07 ` Adrian DC
-- strict thread matches above, loose matches on Subject: below --
2023-10-07 22:30 Javier Tia
2023-10-13 16:03 ` Jon Mason
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=ZvqvFhYoRXQ9RQ4H@kudzu.us \
--to=jdmason@kudzu.us \
--cc=javier.tia@linaro.org \
--cc=jon.mason@arm.com \
--cc=meta-arm@lists.yoctoproject.org \
--cc=radian.dc@gmail.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.