From: Jon Mason <jdmason@kudzu.us>
To: changqing.li@windriver.com
Cc: meta-arm@lists.yoctoproject.org
Subject: Re: [kirkstone][meta-arm][PATCH] optee.inc: update setting for OPTEE_ARCH
Date: Wed, 3 Aug 2022 16:20:53 -0400 [thread overview]
Message-ID: <YurYpbtFhSOH2/n7@kudzu.us> (raw)
In-Reply-To: <20220802062807.4039040-1-changqing.li@windriver.com>
Is this needed on the master branch as well?
Thanks,
Jon
On Tue, Aug 02, 2022 at 02:28:07PM +0800, changqing.li@windriver.com wrote:
> From: Changqing Li <changqing.li@windriver.com>
>
> lib32-optee-os do_compile failed since OPTEE_ARCH is not set correctly.
> In file included from lib/libutee/include/link.h:9,
> from lib/libutee/arch/arm/tcb.c:37:
> lib/libutee/include/elf.h:67:2: error: #error Unknown architecture
> 67 | #error Unknown architecture
> | ^~~~~
> In file included from lib/libutee/arch/arm/tcb.c:37:
> lib/libutee/include/link.h:13:9: error: unknown type name 'Elf_Addr'
> 13 | Elf_Addr dlpi_addr; /* module relocation base */
>
> Signed-off-by: Changqing Li <changqing.li@windriver.com>
> ---
> meta-arm/recipes-security/optee/optee.inc | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta-arm/recipes-security/optee/optee.inc b/meta-arm/recipes-security/optee/optee.inc
> index beae366..2ad7c95 100644
> --- a/meta-arm/recipes-security/optee/optee.inc
> +++ b/meta-arm/recipes-security/optee/optee.inc
> @@ -9,7 +9,7 @@ OPTEEMACHINE ?= "${MACHINE}"
> OPTEEMACHINE:aarch64:qemuall ?= "vexpress-qemu_armv8a"
>
> OPTEE_ARCH = "null"
> -OPTEE_ARCH:armv7a = "arm32"
> +OPTEE_ARCH:arm = "arm32"
> OPTEE_ARCH:aarch64 = "arm64"
> OPTEE_CORE = "${@d.getVar('OPTEE_ARCH').upper()}"
>
> --
> 2.25.1
>
>
next prev parent reply other threads:[~2022-08-03 20:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-02 6:28 [kirkstone][meta-arm][PATCH] optee.inc: update setting for OPTEE_ARCH changqing.li
2022-08-03 20:20 ` Jon Mason [this message]
2022-08-04 1:25 ` Changqing Li
2022-08-08 19:32 ` 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=YurYpbtFhSOH2/n7@kudzu.us \
--to=jdmason@kudzu.us \
--cc=changqing.li@windriver.com \
--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 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.