From: "Khem Raj" <raj.khem@gmail.com>
To: Ross Burton <ross@burtonini.com>,
Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: meta-arm@lists.yoctoproject.org
Subject: Re: [meta-arm][PATCH] meta-arm: Use dynamic layer magic to build trusted-firmware-m
Date: Mon, 6 Jul 2020 10:48:03 -0700 [thread overview]
Message-ID: <8b760e33-101f-3931-147d-c77ca5fac0bb@gmail.com> (raw)
In-Reply-To: <CAAnfSTvZ9GO_hWOJ2Q7=fUQd3EV0b6bVe8T1SdBCwJtrH=4=mg@mail.gmail.com>
On 7/6/20 5:30 AM, Ross Burton wrote:
> Update: Richard has merged the fix. Hopefully that now results in a
> green build!
>
this does not fix the problem for other distributions which are using
meta-arm as dependency. this patch would still be better option IMO to
avoid this dependency when not needed.
> Ross
>
> On Mon, 6 Jul 2020 at 12:07, Ross Burton <ross@burtonini.com> wrote:
>>
>> On Sun, 5 Jul 2020 at 21:15, Richard Purdie
>> <richard.purdie@linuxfoundation.org> wrote:
>>> On Fri, 2020-07-03 at 07:52 -0700, Khem Raj wrote:
>>>> trusted-firmware-m needs arm binary toolchain to build from another
>>>> layer, this is the only recipe thus far and its better to hide it to
>>>> majority users who may not be using trusted-firmware-m and thusly
>>>> meta-arm-toolchain, folks who need to use trusted-firmware-m should
>>>> explicitly add it to layer mix
>>
>> My fault: the layer ordering wasn't quite as important before, but it
>> is now. Testing a fix to autobuilder-helper now.
>>
>> Ross
next prev parent reply other threads:[~2020-07-06 17:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-03 14:52 [meta-arm][PATCH] meta-arm: Use dynamic layer magic to build trusted-firmware-m Khem Raj
2020-07-05 20:15 ` Richard Purdie
2020-07-05 21:29 ` Denys Dmytriyenko
2020-07-06 11:07 ` Ross Burton
2020-07-06 12:30 ` Ross Burton
2020-07-06 17:48 ` Khem Raj [this message]
2020-07-06 21:23 ` Ross Burton
2020-07-07 16:47 ` Khem Raj
2020-07-13 17:09 ` Khem Raj
2020-07-14 10:21 ` Ross Burton
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=8b760e33-101f-3931-147d-c77ca5fac0bb@gmail.com \
--to=raj.khem@gmail.com \
--cc=meta-arm@lists.yoctoproject.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=ross@burtonini.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.