From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>
Cc: Alejandro Vazquez <avazquez.dev@gmail.com>, ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH v2] tf-a: new package for ARM trusted firmware A
Date: Thu, 13 Feb 2020 16:27:02 +0100 [thread overview]
Message-ID: <bbba73db-9e4b-4aae-b2ad-f9078906e79b@pengutronix.de> (raw)
In-Reply-To: <CABDcavYUkTddma=NVs7utgBmDYiK+g5++zdR-TO4aBqcm5owdg@mail.gmail.com>
On 2/13/20 4:24 PM, Guillermo Rodriguez Garcia wrote:
> El jue., 13 feb. 2020 a las 16:08, Ahmad Fatoum
> (<a.fatoum@pengutronix.de>) escribió:
>>
>> On 2/13/20 4:05 PM, Guillermo Rodriguez Garcia wrote:
>>
>>>>>>>
>>>>>>>>>>> +# ----------------------------------------------------------------------------
>>>>>>>>>>> +# Install
>>>>>>>>>>> +# ----------------------------------------------------------------------------
>>>>>>>>>>> +
>>>>>>>>>>> +$(STATEDIR)/tf-a.install:
>>>>>>>>>>> + @$(call targetinfo)
>>>>>>>>>>> +ifeq ($(TF_A_ARTIFACTS_SRC),)
>>>>>>>>>>> + $(warning TF_A_ARTIFACTS is empty. nothing to install.)
>>>>>>>>>>> +else
>>>>>>>>>>> + @install -m644 -D \
>>>>>>>>>>> + --target-directory=$(PTXCONF_SYSROOT_TARGET)/usr/lib/firmware \
>>>>>>>>>>
>>
>>> OK this makes sense.
>>>
>>> But, you should at least make sure
>>> $(PTXCONF_SYSROOT_TARGET)/usr/lib/firmware exists before trying to
>>> copy anything into it.
>>
>> That's why -D is there. From man install(1):
>>
>> -D create all leading components of DEST except the last, or all components of
>> --target-directory, then copy SOURCE to DEST
>
> Yes but the effect of -D combined with --target-directory does not
> seem to be standard; my version of install does not support it.
> The man page for my version says:
>
> -D create all leading components of DEST except the last, then
> copy SOURCE to DEST
>
> And a quick test yields the following:
>
> $ touch test
> $ install -D --target-directory a/b/c test
> install: failed to access 'a/b/c': No such file or director
>
> I guess it's better to avoid relying on that behaviour and create the
> directory explicitly instead.
I see. Will replace with separate install -d in a v3 then.
>
> BR,
>
> Guillermo Rodriguez Garcia
> guille.rodriguez@gmail.com
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | https://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2020-02-13 15:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-12 16:40 Ahmad Fatoum
2020-02-13 12:59 ` Guillermo Rodriguez Garcia
2020-02-13 13:30 ` Ahmad Fatoum
2020-02-13 14:25 ` Guillermo Rodriguez Garcia
2020-02-13 14:28 ` Ahmad Fatoum
2020-02-13 14:32 ` Ahmad Fatoum
2020-02-13 14:35 ` Guillermo Rodriguez Garcia
2020-02-13 14:44 ` Ahmad Fatoum
2020-02-13 14:49 ` Ahmad Fatoum
2020-02-13 15:05 ` Guillermo Rodriguez Garcia
2020-02-13 15:08 ` Ahmad Fatoum
2020-02-13 15:24 ` Guillermo Rodriguez Garcia
2020-02-13 15:27 ` Ahmad Fatoum [this message]
2020-02-13 15:33 ` Guillermo Rodriguez Garcia
2020-02-14 10:57 ` Alex Vazquez
2020-02-14 13:19 ` Michael Olbrich
2020-02-19 10:10 ` Ahmad Fatoum
2020-02-17 16:25 ` Michael Tretter
2020-02-17 16:33 ` Guillermo Rodriguez Garcia
2020-02-18 7:35 ` Michael Olbrich
2020-02-18 9:02 ` Guillermo Rodriguez Garcia
2020-02-19 7:48 ` Michael Tretter
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=bbba73db-9e4b-4aae-b2ad-f9078906e79b@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=avazquez.dev@gmail.com \
--cc=guille.rodriguez@gmail.com \
--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