diff mbox series

[meta-ti,dunfell,1/2] Revert "conf: machine: k3: Add fitImage to the default kernel image types"

Message ID 20221213183818.206660-1-jose.quaresma@foundries.io
State Rejected
Delegated to: Ryan Eatmon
Headers show
Series [meta-ti,dunfell,1/2] Revert "conf: machine: k3: Add fitImage to the default kernel image types" | expand

Commit Message

Jose Quaresma Dec. 13, 2022, 6:38 p.m. UTC 
This reverts commit e6deeba806d2145fa16b0b5f444f2985e63e6366.

Currently building with am62xx-evm/am64xx-evm machine fails with:

| make[1]: *** No rule to make target 'fitImage'.  Stop.
| make: *** [/build/tmp/work-shared/am62xx-evm/kernel-source/Makefile:185: __sub-make] Error 2
| ERROR: oe_runmake failed

Signed-off-by: Jose Quaresma <jose.quaresma@foundries.io>
---
 conf/machine/include/k3.inc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Comments

Ryan Eatmon Dec. 13, 2022, 8:03 p.m. UTC | #1 
On 12/13/2022 12:38, Jose Quaresma wrote:
> This reverts commit e6deeba806d2145fa16b0b5f444f2985e63e6366.
> 
> Currently building with am62xx-evm/am64xx-evm machine fails with:
> 
> | make[1]: *** No rule to make target 'fitImage'.  Stop.
> | make: *** [/build/tmp/work-shared/am62xx-evm/kernel-source/Makefile:185: __sub-make] Error 2
> | ERROR: oe_runmake failed

This is a little surprising as we build dunfell every night without 
issue.  Are you using the linux-ti-staging kernel in your build?


> Signed-off-by: Jose Quaresma <jose.quaresma@foundries.io>
> ---
>   conf/machine/include/k3.inc | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/conf/machine/include/k3.inc b/conf/machine/include/k3.inc
> index 349f4fda..ef4f107f 100644
> --- a/conf/machine/include/k3.inc
> +++ b/conf/machine/include/k3.inc
> @@ -15,7 +15,7 @@ PREFERRED_PROVIDER_virtual/bootloader = "u-boot-ti-staging"
>   PREFERRED_PROVIDER_u-boot = "u-boot-ti-staging"
>   
>   KERNEL_IMAGETYPE = "Image"
> -KERNEL_IMAGETYPES = "Image fitImage"
> +KERNEL_IMAGETYPES = "Image"
>   
>   UBOOT_ARCH = "arm"
>   UBOOT_ENTRYPOINT = "0x80008000"
> 
> 
> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#15465): https://lists.yoctoproject.org/g/meta-ti/message/15465
> Mute This Topic: https://lists.yoctoproject.org/mt/95650880/6551054
> Group Owner: meta-ti+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub [reatmon@ti.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
Denys Dmytriyenko Dec. 13, 2022, 9:06 p.m. UTC | #2 
On Tue, Dec 13, 2022 at 06:38:17PM +0000, Jose Quaresma wrote:
> This reverts commit e6deeba806d2145fa16b0b5f444f2985e63e6366.

NAK. There's a fix in kirkstone/master...


> Currently building with am62xx-evm/am64xx-evm machine fails with:
> 
> | make[1]: *** No rule to make target 'fitImage'.  Stop.
> | make: *** [/build/tmp/work-shared/am62xx-evm/kernel-source/Makefile:185: __sub-make] Error 2
> | ERROR: oe_runmake failed
> 
> Signed-off-by: Jose Quaresma <jose.quaresma@foundries.io>
> ---
>  conf/machine/include/k3.inc | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/conf/machine/include/k3.inc b/conf/machine/include/k3.inc
> index 349f4fda..ef4f107f 100644
> --- a/conf/machine/include/k3.inc
> +++ b/conf/machine/include/k3.inc
> @@ -15,7 +15,7 @@ PREFERRED_PROVIDER_virtual/bootloader = "u-boot-ti-staging"
>  PREFERRED_PROVIDER_u-boot = "u-boot-ti-staging"
>  
>  KERNEL_IMAGETYPE = "Image"
> -KERNEL_IMAGETYPES = "Image fitImage"
> +KERNEL_IMAGETYPES = "Image"
>  
>  UBOOT_ARCH = "arm"
>  UBOOT_ENTRYPOINT = "0x80008000"
> -- 
> 2.38.2
>
Jose Quaresma Dec. 14, 2022, 9:29 a.m. UTC | #3 
Ryan Eatmon <reatmon@ti.com> escreveu no dia terça, 13/12/2022 à(s) 20:03:

>
>
> On 12/13/2022 12:38, Jose Quaresma wrote:
> > This reverts commit e6deeba806d2145fa16b0b5f444f2985e63e6366.
> >
> > Currently building with am62xx-evm/am64xx-evm machine fails with:
> >
> > | make[1]: *** No rule to make target 'fitImage'.  Stop.
> > | make: ***
> [/build/tmp/work-shared/am62xx-evm/kernel-source/Makefile:185: __sub-make]
> Error 2
> > | ERROR: oe_runmake failed
>
> This is a little surprising as we build dunfell every night without
> issue.  Are you using the linux-ti-staging kernel in your build?
>

I am building only with the bsp layer and with the default configuration.

Build Configuration:
BB_VERSION           = "1.46.0"
BUILD_SYS            = "x86_64-linux"
NATIVELSBSTRING      = "universal"
TARGET_SYS           = "aarch64-poky-linux"
MACHINE              = "am62xx-evm"
DISTRO               = "poky"
DISTRO_VERSION       = "3.1.21"
TUNE_FEATURES        = "aarch64"
TARGET_FPU           = ""
meta-arm
meta-arm-toolchain   = "dunfell:08c44df351ae1913f41de8388981b03e21235f09"
meta-ti              = "dunfell:00f616fad364ba3ceffc35097ecd0c8d247ad52e"
meta-oe
meta-python          = "dunfell:7203130ed8b58c0df75cb72222ac2bcf546bce44"
meta
meta-poky            = "dunfell:3155eb565fb1758ba426ab7f5ea710004ccbeb58"

The layer meta-oe/meta-python is a dependency of the meta-arm for
python3-cryptography native:

ERROR: Nothing PROVIDES 'python3-cryptography-native' (but
/build/../work/meta-arm/meta-arm/recipes-security/optee/optee-os_git.bb
DEPENDS on or otherwise requires it). Close matches:

The default kernel is the linux-ti-staging:

ERROR: Task
(/build/../work/meta-ti/recipes-kernel/linux/linux-ti-staging_5.10.bb:do_compile)
failed with exit code '1'


>
>
> > Signed-off-by: Jose Quaresma <jose.quaresma@foundries.io>
> > ---
> >   conf/machine/include/k3.inc | 2 +-
> >   1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/conf/machine/include/k3.inc b/conf/machine/include/k3.inc
> > index 349f4fda..ef4f107f 100644
> > --- a/conf/machine/include/k3.inc
> > +++ b/conf/machine/include/k3.inc
> > @@ -15,7 +15,7 @@ PREFERRED_PROVIDER_virtual/bootloader =
> "u-boot-ti-staging"
> >   PREFERRED_PROVIDER_u-boot = "u-boot-ti-staging"
> >
> >   KERNEL_IMAGETYPE = "Image"
> > -KERNEL_IMAGETYPES = "Image fitImage"
> > +KERNEL_IMAGETYPES = "Image"
> >
> >   UBOOT_ARCH = "arm"
> >   UBOOT_ENTRYPOINT = "0x80008000"
> >
> >
> >
> > -=-=-=-=-=-=-=-=-=-=-=-
> > Links: You receive all messages sent to this group.
> > View/Reply Online (#15465):
> https://lists.yoctoproject.org/g/meta-ti/message/15465
> > Mute This Topic: https://lists.yoctoproject.org/mt/95650880/6551054
> > Group Owner: meta-ti+owner@lists.yoctoproject.org
> > Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub [
> reatmon@ti.com]
> > -=-=-=-=-=-=-=-=-=-=-=-
> >
>
> --
> Ryan Eatmon                reatmon@ti.com
> -----------------------------------------
> Texas Instruments, Inc.  -  LCPD  -  MGTS
>
Jose Quaresma Jan. 4, 2023, 7:18 p.m. UTC | #4 
Friendly ping :)

thanks

Jose Quaresma via lists.yoctoproject.org <quaresma.jose=
gmail.com@lists.yoctoproject.org> escreveu no dia terça, 13/12/2022 à(s)
18:38:

> f8182afd optee: Upgrade to upstream 3.17.0
> removes this patch but this is still required
>
> Currently building with am62xx-evm/am64xx-evm machine fails with:
>
> | aarch64-poky-linux-ld.bfd: cannot find libgcc.a: No such file or
> directory
> | make: *** [ldelf/link.mk:60: out/arm-plat-k3/ldelf/ldelf.elf] Error 1
> | make: *** Waiting for unfinished jobs....
>
> Signed-off-by: Jose Quaresma <jose.quaresma@foundries.io>
> ---
>  ...ow-setting-sysroot-for-libgcc-lookup.patch | 34 +++++++++++++++++++
>  recipes-security/optee/optee-os_%.bbappend    |  6 +++-
>  2 files changed, 39 insertions(+), 1 deletion(-)
>  create mode 100644
> recipes-security/optee/optee-os/0006-allow-setting-sysroot-for-libgcc-lookup.patch
>
> diff --git
> a/recipes-security/optee/optee-os/0006-allow-setting-sysroot-for-libgcc-lookup.patch
> b/recipes-security/optee/optee-os/0006-allow-setting-sysroot-for-libgcc-lookup.patch
> new file mode 100644
> index 00000000..17005396
> --- /dev/null
> +++
> b/recipes-security/optee/optee-os/0006-allow-setting-sysroot-for-libgcc-lookup.patch
> @@ -0,0 +1,34 @@
> +From 0bab935695ebcf0c533b49896ab18ff33d4a47d1 Mon Sep 17 00:00:00 2001
> +From: Ross Burton <ross.burton@arm.com>
> +Date: Tue, 26 May 2020 14:38:02 -0500
> +Subject: [PATCH] allow setting sysroot for libgcc lookup
> +
> +Explicitly pass the new variable LIBGCC_LOCATE_CFLAGS variable when
> searching
> +for the compiler libraries as there's no easy way to reliably pass
> --sysroot
> +otherwise.
> +
> +Upstream-Status: Pending [https://github.com/OP-TEE/optee_os/issues/4188]
> +Signed-off-by: Ross Burton <ross.burton@arm.com>
> +---
> + mk/gcc.mk | 6 +++---
> + 1 file changed, 3 insertions(+), 3 deletions(-)
> +
> +diff --git a/mk/gcc.mk b/mk/gcc.mk
> +index adc77a24..81bfa78a 100644
> +--- a/mk/gcc.mk
> ++++ b/mk/gcc.mk
> +@@ -13,11 +13,11 @@ nostdinc$(sm)      := -nostdinc -isystem $(shell
> $(CC$(sm)) \
> +                       -print-file-name=include 2> /dev/null)
> +
> + # Get location of libgcc from gcc
> +-libgcc$(sm)   := $(shell $(CC$(sm)) $(CFLAGS$(arch-bits-$(sm))) \
> ++libgcc$(sm)   := $(shell $(CC$(sm)) $(LIBGCC_LOCATE_CFLAGS)
> $(CFLAGS$(arch-bits-$(sm))) \
> +                       -print-libgcc-file-name 2> /dev/null)
> +-libstdc++$(sm)        := $(shell $(CXX$(sm))
> $(CXXFLAGS$(arch-bits-$(sm))) $(comp-cxxflags$(sm)) \
> ++libstdc++$(sm)        := $(shell $(CXX$(sm)) $(LIBGCC_LOCATE_CFLAGS)
> $(CXXFLAGS$(arch-bits-$(sm))) $(comp-cxxflags$(sm)) \
> +                       -print-file-name=libstdc++.a 2> /dev/null)
> +-libgcc_eh$(sm)        := $(shell $(CXX$(sm))
> $(CXXFLAGS$(arch-bits-$(sm))) $(comp-cxxflags$(sm)) \
> ++libgcc_eh$(sm)        := $(shell $(CXX$(sm)) $(LIBGCC_LOCATE_CFLAGS)
> $(CXXFLAGS$(arch-bits-$(sm))) $(comp-cxxflags$(sm)) \
> +                       -print-file-name=libgcc_eh.a 2> /dev/null)
> +
> + # Define these to something to discover accidental use
> diff --git a/recipes-security/optee/optee-os_%.bbappend
> b/recipes-security/optee/optee-os_%.bbappend
> index 751dc3d0..e8af0124 100644
> --- a/recipes-security/optee/optee-os_%.bbappend
> +++ b/recipes-security/optee/optee-os_%.bbappend
> @@ -1,6 +1,10 @@
> +FILESEXTRAPATHS_prepend_ti-soc := "${THISDIR}/${PN}:"
> +
>  PV_ti-soc = "3.19.0+git${SRCPV}"
>  SRCREV_ti-soc = "d6c5d0037b46f46caf71d67d7825d4b722cbcddf"
> -SRC_URI_ti-soc = "git://github.com/OP-TEE/optee_os.git;protocol=https"
> +SRC_URI_ti-soc = "git://github.com/OP-TEE/optee_os.git;protocol=https \
> +    file://0006-allow-setting-sysroot-for-libgcc-lookup.patch \
> +"
>
>  DEPENDS_append_ti-soc = " python3-cryptography-native"
>
> --
> 2.38.2
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#15466):
> https://lists.yoctoproject.org/g/meta-ti/message/15466
> Mute This Topic: https://lists.yoctoproject.org/mt/95650881/5052612
> Group Owner: meta-ti+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub [
> quaresma.jose@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>
Denys Dmytriyenko Jan. 4, 2023, 8:54 p.m. UTC | #5 
Not being able to reproduce the issue here:

$ MACHINE=am64xx-evm bitbake optee-os

Builds just fine.

Any more pointers - host OS/version, etc? I'm building Dunfell in Ubuntu 18.04 
container, but can try a newer one if that's the culprit.


On Wed, Jan 04, 2023 at 07:18:50PM +0000, Jose Quaresma wrote:
> Friendly ping :)
> 
> thanks
> 
> Jose Quaresma via lists.yoctoproject.org <quaresma.jose=
> gmail.com@lists.yoctoproject.org> escreveu no dia terça, 13/12/2022 à(s)
> 18:38:
> 
> > f8182afd optee: Upgrade to upstream 3.17.0
> > removes this patch but this is still required
> >
> > Currently building with am62xx-evm/am64xx-evm machine fails with:
> >
> > | aarch64-poky-linux-ld.bfd: cannot find libgcc.a: No such file or
> > directory
> > | make: *** [ldelf/link.mk:60: out/arm-plat-k3/ldelf/ldelf.elf] Error 1
> > | make: *** Waiting for unfinished jobs....
> >
> > Signed-off-by: Jose Quaresma <jose.quaresma@foundries.io>
> > ---
> >  ...ow-setting-sysroot-for-libgcc-lookup.patch | 34 +++++++++++++++++++
> >  recipes-security/optee/optee-os_%.bbappend    |  6 +++-
> >  2 files changed, 39 insertions(+), 1 deletion(-)
> >  create mode 100644
> > recipes-security/optee/optee-os/0006-allow-setting-sysroot-for-libgcc-lookup.patch
> >
> > diff --git
> > a/recipes-security/optee/optee-os/0006-allow-setting-sysroot-for-libgcc-lookup.patch
> > b/recipes-security/optee/optee-os/0006-allow-setting-sysroot-for-libgcc-lookup.patch
> > new file mode 100644
> > index 00000000..17005396
> > --- /dev/null
> > +++
> > b/recipes-security/optee/optee-os/0006-allow-setting-sysroot-for-libgcc-lookup.patch
> > @@ -0,0 +1,34 @@
> > +From 0bab935695ebcf0c533b49896ab18ff33d4a47d1 Mon Sep 17 00:00:00 2001
> > +From: Ross Burton <ross.burton@arm.com>
> > +Date: Tue, 26 May 2020 14:38:02 -0500
> > +Subject: [PATCH] allow setting sysroot for libgcc lookup
> > +
> > +Explicitly pass the new variable LIBGCC_LOCATE_CFLAGS variable when
> > searching
> > +for the compiler libraries as there's no easy way to reliably pass
> > --sysroot
> > +otherwise.
> > +
> > +Upstream-Status: Pending [https://github.com/OP-TEE/optee_os/issues/4188]
> > +Signed-off-by: Ross Burton <ross.burton@arm.com>
> > +---
> > + mk/gcc.mk | 6 +++---
> > + 1 file changed, 3 insertions(+), 3 deletions(-)
> > +
> > +diff --git a/mk/gcc.mk b/mk/gcc.mk
> > +index adc77a24..81bfa78a 100644
> > +--- a/mk/gcc.mk
> > ++++ b/mk/gcc.mk
> > +@@ -13,11 +13,11 @@ nostdinc$(sm)      := -nostdinc -isystem $(shell
> > $(CC$(sm)) \
> > +                       -print-file-name=include 2> /dev/null)
> > +
> > + # Get location of libgcc from gcc
> > +-libgcc$(sm)   := $(shell $(CC$(sm)) $(CFLAGS$(arch-bits-$(sm))) \
> > ++libgcc$(sm)   := $(shell $(CC$(sm)) $(LIBGCC_LOCATE_CFLAGS)
> > $(CFLAGS$(arch-bits-$(sm))) \
> > +                       -print-libgcc-file-name 2> /dev/null)
> > +-libstdc++$(sm)        := $(shell $(CXX$(sm))
> > $(CXXFLAGS$(arch-bits-$(sm))) $(comp-cxxflags$(sm)) \
> > ++libstdc++$(sm)        := $(shell $(CXX$(sm)) $(LIBGCC_LOCATE_CFLAGS)
> > $(CXXFLAGS$(arch-bits-$(sm))) $(comp-cxxflags$(sm)) \
> > +                       -print-file-name=libstdc++.a 2> /dev/null)
> > +-libgcc_eh$(sm)        := $(shell $(CXX$(sm))
> > $(CXXFLAGS$(arch-bits-$(sm))) $(comp-cxxflags$(sm)) \
> > ++libgcc_eh$(sm)        := $(shell $(CXX$(sm)) $(LIBGCC_LOCATE_CFLAGS)
> > $(CXXFLAGS$(arch-bits-$(sm))) $(comp-cxxflags$(sm)) \
> > +                       -print-file-name=libgcc_eh.a 2> /dev/null)
> > +
> > + # Define these to something to discover accidental use
> > diff --git a/recipes-security/optee/optee-os_%.bbappend
> > b/recipes-security/optee/optee-os_%.bbappend
> > index 751dc3d0..e8af0124 100644
> > --- a/recipes-security/optee/optee-os_%.bbappend
> > +++ b/recipes-security/optee/optee-os_%.bbappend
> > @@ -1,6 +1,10 @@
> > +FILESEXTRAPATHS_prepend_ti-soc := "${THISDIR}/${PN}:"
> > +
> >  PV_ti-soc = "3.19.0+git${SRCPV}"
> >  SRCREV_ti-soc = "d6c5d0037b46f46caf71d67d7825d4b722cbcddf"
> > -SRC_URI_ti-soc = "git://github.com/OP-TEE/optee_os.git;protocol=https"
> > +SRC_URI_ti-soc = "git://github.com/OP-TEE/optee_os.git;protocol=https \
> > +    file://0006-allow-setting-sysroot-for-libgcc-lookup.patch \
> > +"
> >
> >  DEPENDS_append_ti-soc = " python3-cryptography-native"
> >
> > --
> > 2.38.2
> >
> >
> > 
> >
> >
Jose Quaresma Jan. 5, 2023, 10:44 a.m. UTC | #6 
Hi Denys,

I can reproduce this issue with kas and using their container that is
debian 11 based.

builder@96ee80f74a76:/build$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux 11 (bullseye)
Release:        11
Codename:       bullseye


The ti-dunfell-optee.yml reproduces the issue and
the ti-dunfell-optee-fixed.yml uses this patch.
Here is the steps to reproduce:

# kas install
mkdir -p ti-dunfell-optee && \
cd ti-dunfell-optee && \
python -m venv kas && \
source kas/bin/activate && \
pip install kas

# kas config
cat <<EOF > ti-dunfell-optee.yml
header:
  version: 8

local_conf_header:
  poky: |
    DISTRO_FEATURES:remove = "ptest"

distro: poky

target: optee-os

defaults:
  repos:
    refspec: dunfell

repos:
  poky:
    url: https://git.yoctoproject.org/git/poky
    layers:
      meta:
      meta-poky:

  meta-ti:
    url: "https://git.yoctoproject.org/meta-ti"

  meta-arm:
    url: "https://git.yoctoproject.org/meta-arm"
    layers:
      meta-arm:
      meta-arm-toolchain:

  meta-openembedded:
    url: "https://git.openembedded.org/meta-openembedded"
    layers:
      meta-oe:
      meta-python:
EOF

# kas build
KAS_MACHINE=am62xx-evm kas-container build ti-dunfell-optee.yml
KAS_MACHINE=am64xx-evm kas-container build ti-dunfell-optee.yml

# kas config
# patch path:
ti-dunfell-optee/0001-optee-os-add-back-allow-setting-sysroot-for-libgcc-l.patch
cat <<EOF > ti-dunfell-optee-fixed.yml
header:
  version: 8
  includes:
    - ti-dunfell-optee.yml

repos:
  meta-ti:
    patches:
      libgcc:
        repo: meta-ti
        path:
../0001-optee-os-add-back-allow-setting-sysroot-for-libgcc-l.patch
EOF

# kas build
KAS_MACHINE=am62xx-evm kas-container build ti-dunfell-optee.yml
KAS_MACHINE=am64xx-evm kas-container build ti-dunfell-optee.yml

Jose

Denys Dmytriyenko <denis@denix.org> escreveu no dia quarta, 4/01/2023 à(s)
20:54:

> Not being able to reproduce the issue here:
>
> $ MACHINE=am64xx-evm bitbake optee-os
>
> Builds just fine.
>
> Any more pointers - host OS/version, etc? I'm building Dunfell in Ubuntu
> 18.04
> container, but can try a newer one if that's the culprit.
>
>
> On Wed, Jan 04, 2023 at 07:18:50PM +0000, Jose Quaresma wrote:
> > Friendly ping :)
> >
> > thanks
> >
> > Jose Quaresma via lists.yoctoproject.org <quaresma.jose=
> > gmail.com@lists.yoctoproject.org> escreveu no dia terça, 13/12/2022 à(s)
> > 18:38:
> >
> > > f8182afd optee: Upgrade to upstream 3.17.0
> > > removes this patch but this is still required
> > >
> > > Currently building with am62xx-evm/am64xx-evm machine fails with:
> > >
> > > | aarch64-poky-linux-ld.bfd: cannot find libgcc.a: No such file or
> > > directory
> > > | make: *** [ldelf/link.mk:60: out/arm-plat-k3/ldelf/ldelf.elf] Error
> 1
> > > | make: *** Waiting for unfinished jobs....
> > >
> > > Signed-off-by: Jose Quaresma <jose.quaresma@foundries.io>
> > > ---
> > >  ...ow-setting-sysroot-for-libgcc-lookup.patch | 34 +++++++++++++++++++
> > >  recipes-security/optee/optee-os_%.bbappend    |  6 +++-
> > >  2 files changed, 39 insertions(+), 1 deletion(-)
> > >  create mode 100644
> > >
> recipes-security/optee/optee-os/0006-allow-setting-sysroot-for-libgcc-lookup.patch
> > >
> > > diff --git
> > >
> a/recipes-security/optee/optee-os/0006-allow-setting-sysroot-for-libgcc-lookup.patch
> > >
> b/recipes-security/optee/optee-os/0006-allow-setting-sysroot-for-libgcc-lookup.patch
> > > new file mode 100644
> > > index 00000000..17005396
> > > --- /dev/null
> > > +++
> > >
> b/recipes-security/optee/optee-os/0006-allow-setting-sysroot-for-libgcc-lookup.patch
> > > @@ -0,0 +1,34 @@
> > > +From 0bab935695ebcf0c533b49896ab18ff33d4a47d1 Mon Sep 17 00:00:00 2001
> > > +From: Ross Burton <ross.burton@arm.com>
> > > +Date: Tue, 26 May 2020 14:38:02 -0500
> > > +Subject: [PATCH] allow setting sysroot for libgcc lookup
> > > +
> > > +Explicitly pass the new variable LIBGCC_LOCATE_CFLAGS variable when
> > > searching
> > > +for the compiler libraries as there's no easy way to reliably pass
> > > --sysroot
> > > +otherwise.
> > > +
> > > +Upstream-Status: Pending [
> https://github.com/OP-TEE/optee_os/issues/4188]
> > > +Signed-off-by: Ross Burton <ross.burton@arm.com>
> > > +---
> > > + mk/gcc.mk | 6 +++---
> > > + 1 file changed, 3 insertions(+), 3 deletions(-)
> > > +
> > > +diff --git a/mk/gcc.mk b/mk/gcc.mk
> > > +index adc77a24..81bfa78a 100644
> > > +--- a/mk/gcc.mk
> > > ++++ b/mk/gcc.mk
> > > +@@ -13,11 +13,11 @@ nostdinc$(sm)      := -nostdinc -isystem $(shell
> > > $(CC$(sm)) \
> > > +                       -print-file-name=include 2> /dev/null)
> > > +
> > > + # Get location of libgcc from gcc
> > > +-libgcc$(sm)   := $(shell $(CC$(sm)) $(CFLAGS$(arch-bits-$(sm))) \
> > > ++libgcc$(sm)   := $(shell $(CC$(sm)) $(LIBGCC_LOCATE_CFLAGS)
> > > $(CFLAGS$(arch-bits-$(sm))) \
> > > +                       -print-libgcc-file-name 2> /dev/null)
> > > +-libstdc++$(sm)        := $(shell $(CXX$(sm))
> > > $(CXXFLAGS$(arch-bits-$(sm))) $(comp-cxxflags$(sm)) \
> > > ++libstdc++$(sm)        := $(shell $(CXX$(sm)) $(LIBGCC_LOCATE_CFLAGS)
> > > $(CXXFLAGS$(arch-bits-$(sm))) $(comp-cxxflags$(sm)) \
> > > +                       -print-file-name=libstdc++.a 2> /dev/null)
> > > +-libgcc_eh$(sm)        := $(shell $(CXX$(sm))
> > > $(CXXFLAGS$(arch-bits-$(sm))) $(comp-cxxflags$(sm)) \
> > > ++libgcc_eh$(sm)        := $(shell $(CXX$(sm)) $(LIBGCC_LOCATE_CFLAGS)
> > > $(CXXFLAGS$(arch-bits-$(sm))) $(comp-cxxflags$(sm)) \
> > > +                       -print-file-name=libgcc_eh.a 2> /dev/null)
> > > +
> > > + # Define these to something to discover accidental use
> > > diff --git a/recipes-security/optee/optee-os_%.bbappend
> > > b/recipes-security/optee/optee-os_%.bbappend
> > > index 751dc3d0..e8af0124 100644
> > > --- a/recipes-security/optee/optee-os_%.bbappend
> > > +++ b/recipes-security/optee/optee-os_%.bbappend
> > > @@ -1,6 +1,10 @@
> > > +FILESEXTRAPATHS_prepend_ti-soc := "${THISDIR}/${PN}:"
> > > +
> > >  PV_ti-soc = "3.19.0+git${SRCPV}"
> > >  SRCREV_ti-soc = "d6c5d0037b46f46caf71d67d7825d4b722cbcddf"
> > > -SRC_URI_ti-soc = "git://github.com/OP-TEE/optee_os.git;protocol=https
> "
> > > +SRC_URI_ti-soc = "git://github.com/OP-TEE/optee_os.git;protocol=https
> \
> > > +    file://0006-allow-setting-sysroot-for-libgcc-lookup.patch \
> > > +"
> > >
> > >  DEPENDS_append_ti-soc = " python3-cryptography-native"
> > >
> > > --
> > > 2.38.2
> > >
> > >
> > >
> > >
> > >
>
Denys Dmytriyenko Jan. 10, 2023, 11:38 p.m. UTC | #7 
Ok, this is not specific to the host OS.

It is toolchain-specific though - it doesn't fail with the external Arm 
toolchain, but fails with the toolchain built by OE, i.e. Poky, etc.


On Wed, Jan 04, 2023 at 03:54:05PM -0500, Denys Dmytriyenko wrote:
> Not being able to reproduce the issue here:
> 
> $ MACHINE=am64xx-evm bitbake optee-os
> 
> Builds just fine.
> 
> Any more pointers - host OS/version, etc? I'm building Dunfell in Ubuntu 18.04 
> container, but can try a newer one if that's the culprit.
> 
> 
> On Wed, Jan 04, 2023 at 07:18:50PM +0000, Jose Quaresma wrote:
> > Friendly ping :)
> > 
> > thanks
> > 
> > Jose Quaresma via lists.yoctoproject.org <quaresma.jose=
> > gmail.com@lists.yoctoproject.org> escreveu no dia terça, 13/12/2022 à(s)
> > 18:38:
> > 
> > > f8182afd optee: Upgrade to upstream 3.17.0
> > > removes this patch but this is still required
> > >
> > > Currently building with am62xx-evm/am64xx-evm machine fails with:
> > >
> > > | aarch64-poky-linux-ld.bfd: cannot find libgcc.a: No such file or
> > > directory
> > > | make: *** [ldelf/link.mk:60: out/arm-plat-k3/ldelf/ldelf.elf] Error 1
> > > | make: *** Waiting for unfinished jobs....
> > >
> > > Signed-off-by: Jose Quaresma <jose.quaresma@foundries.io>
> > > ---
> > >  ...ow-setting-sysroot-for-libgcc-lookup.patch | 34 +++++++++++++++++++
> > >  recipes-security/optee/optee-os_%.bbappend    |  6 +++-
> > >  2 files changed, 39 insertions(+), 1 deletion(-)
> > >  create mode 100644
> > > recipes-security/optee/optee-os/0006-allow-setting-sysroot-for-libgcc-lookup.patch
> > >
> > > diff --git
> > > a/recipes-security/optee/optee-os/0006-allow-setting-sysroot-for-libgcc-lookup.patch
> > > b/recipes-security/optee/optee-os/0006-allow-setting-sysroot-for-libgcc-lookup.patch
> > > new file mode 100644
> > > index 00000000..17005396
> > > --- /dev/null
> > > +++
> > > b/recipes-security/optee/optee-os/0006-allow-setting-sysroot-for-libgcc-lookup.patch
> > > @@ -0,0 +1,34 @@
> > > +From 0bab935695ebcf0c533b49896ab18ff33d4a47d1 Mon Sep 17 00:00:00 2001
> > > +From: Ross Burton <ross.burton@arm.com>
> > > +Date: Tue, 26 May 2020 14:38:02 -0500
> > > +Subject: [PATCH] allow setting sysroot for libgcc lookup
> > > +
> > > +Explicitly pass the new variable LIBGCC_LOCATE_CFLAGS variable when
> > > searching
> > > +for the compiler libraries as there's no easy way to reliably pass
> > > --sysroot
> > > +otherwise.
> > > +
> > > +Upstream-Status: Pending [https://github.com/OP-TEE/optee_os/issues/4188]
> > > +Signed-off-by: Ross Burton <ross.burton@arm.com>
> > > +---
> > > + mk/gcc.mk | 6 +++---
> > > + 1 file changed, 3 insertions(+), 3 deletions(-)
> > > +
> > > +diff --git a/mk/gcc.mk b/mk/gcc.mk
> > > +index adc77a24..81bfa78a 100644
> > > +--- a/mk/gcc.mk
> > > ++++ b/mk/gcc.mk
> > > +@@ -13,11 +13,11 @@ nostdinc$(sm)      := -nostdinc -isystem $(shell
> > > $(CC$(sm)) \
> > > +                       -print-file-name=include 2> /dev/null)
> > > +
> > > + # Get location of libgcc from gcc
> > > +-libgcc$(sm)   := $(shell $(CC$(sm)) $(CFLAGS$(arch-bits-$(sm))) \
> > > ++libgcc$(sm)   := $(shell $(CC$(sm)) $(LIBGCC_LOCATE_CFLAGS)
> > > $(CFLAGS$(arch-bits-$(sm))) \
> > > +                       -print-libgcc-file-name 2> /dev/null)
> > > +-libstdc++$(sm)        := $(shell $(CXX$(sm))
> > > $(CXXFLAGS$(arch-bits-$(sm))) $(comp-cxxflags$(sm)) \
> > > ++libstdc++$(sm)        := $(shell $(CXX$(sm)) $(LIBGCC_LOCATE_CFLAGS)
> > > $(CXXFLAGS$(arch-bits-$(sm))) $(comp-cxxflags$(sm)) \
> > > +                       -print-file-name=libstdc++.a 2> /dev/null)
> > > +-libgcc_eh$(sm)        := $(shell $(CXX$(sm))
> > > $(CXXFLAGS$(arch-bits-$(sm))) $(comp-cxxflags$(sm)) \
> > > ++libgcc_eh$(sm)        := $(shell $(CXX$(sm)) $(LIBGCC_LOCATE_CFLAGS)
> > > $(CXXFLAGS$(arch-bits-$(sm))) $(comp-cxxflags$(sm)) \
> > > +                       -print-file-name=libgcc_eh.a 2> /dev/null)
> > > +
> > > + # Define these to something to discover accidental use
> > > diff --git a/recipes-security/optee/optee-os_%.bbappend
> > > b/recipes-security/optee/optee-os_%.bbappend
> > > index 751dc3d0..e8af0124 100644
> > > --- a/recipes-security/optee/optee-os_%.bbappend
> > > +++ b/recipes-security/optee/optee-os_%.bbappend
> > > @@ -1,6 +1,10 @@
> > > +FILESEXTRAPATHS_prepend_ti-soc := "${THISDIR}/${PN}:"
> > > +
> > >  PV_ti-soc = "3.19.0+git${SRCPV}"
> > >  SRCREV_ti-soc = "d6c5d0037b46f46caf71d67d7825d4b722cbcddf"
> > > -SRC_URI_ti-soc = "git://github.com/OP-TEE/optee_os.git;protocol=https"
> > > +SRC_URI_ti-soc = "git://github.com/OP-TEE/optee_os.git;protocol=https \
> > > +    file://0006-allow-setting-sysroot-for-libgcc-lookup.patch \
> > > +"
> > >
> > >  DEPENDS_append_ti-soc = " python3-cryptography-native"
> > >
> > > --
> > > 2.38.2
Jose Quaresma Jan. 11, 2023, 10:13 a.m. UTC | #8 
Denys Dmytriyenko <denis@denix.org> escreveu no dia terça, 10/01/2023 à(s)
23:39:

> Ok, this is not specific to the host OS.
>
> It is toolchain-specific though - it doesn't fail with the external Arm
> toolchain, but fails with the toolchain built by OE, i.e. Poky, etc.
>

So this can be the reason to build with meta-arago and not without it.
Thanks for looking at this.

Jose


>
> On Wed, Jan 04, 2023 at 03:54:05PM -0500, Denys Dmytriyenko wrote:
> > Not being able to reproduce the issue here:
> >
> > $ MACHINE=am64xx-evm bitbake optee-os
> >
> > Builds just fine.
> >
> > Any more pointers - host OS/version, etc? I'm building Dunfell in Ubuntu
> 18.04
> > container, but can try a newer one if that's the culprit.
> >
> >
> > On Wed, Jan 04, 2023 at 07:18:50PM +0000, Jose Quaresma wrote:
> > > Friendly ping :)
> > >
> > > thanks
> > >
> > > Jose Quaresma via lists.yoctoproject.org <quaresma.jose=
> > > gmail.com@lists.yoctoproject.org> escreveu no dia terça, 13/12/2022
> à(s)
> > > 18:38:
> > >
> > > > f8182afd optee: Upgrade to upstream 3.17.0
> > > > removes this patch but this is still required
> > > >
> > > > Currently building with am62xx-evm/am64xx-evm machine fails with:
> > > >
> > > > | aarch64-poky-linux-ld.bfd: cannot find libgcc.a: No such file or
> > > > directory
> > > > | make: *** [ldelf/link.mk:60: out/arm-plat-k3/ldelf/ldelf.elf]
> Error 1
> > > > | make: *** Waiting for unfinished jobs....
> > > >
> > > > Signed-off-by: Jose Quaresma <jose.quaresma@foundries.io>
> > > > ---
> > > >  ...ow-setting-sysroot-for-libgcc-lookup.patch | 34
> +++++++++++++++++++
> > > >  recipes-security/optee/optee-os_%.bbappend    |  6 +++-
> > > >  2 files changed, 39 insertions(+), 1 deletion(-)
> > > >  create mode 100644
> > > >
> recipes-security/optee/optee-os/0006-allow-setting-sysroot-for-libgcc-lookup.patch
> > > >
> > > > diff --git
> > > >
> a/recipes-security/optee/optee-os/0006-allow-setting-sysroot-for-libgcc-lookup.patch
> > > >
> b/recipes-security/optee/optee-os/0006-allow-setting-sysroot-for-libgcc-lookup.patch
> > > > new file mode 100644
> > > > index 00000000..17005396
> > > > --- /dev/null
> > > > +++
> > > >
> b/recipes-security/optee/optee-os/0006-allow-setting-sysroot-for-libgcc-lookup.patch
> > > > @@ -0,0 +1,34 @@
> > > > +From 0bab935695ebcf0c533b49896ab18ff33d4a47d1 Mon Sep 17 00:00:00
> 2001
> > > > +From: Ross Burton <ross.burton@arm.com>
> > > > +Date: Tue, 26 May 2020 14:38:02 -0500
> > > > +Subject: [PATCH] allow setting sysroot for libgcc lookup
> > > > +
> > > > +Explicitly pass the new variable LIBGCC_LOCATE_CFLAGS variable when
> > > > searching
> > > > +for the compiler libraries as there's no easy way to reliably pass
> > > > --sysroot
> > > > +otherwise.
> > > > +
> > > > +Upstream-Status: Pending [
> https://github.com/OP-TEE/optee_os/issues/4188]
> > > > +Signed-off-by: Ross Burton <ross.burton@arm.com>
> > > > +---
> > > > + mk/gcc.mk | 6 +++---
> > > > + 1 file changed, 3 insertions(+), 3 deletions(-)
> > > > +
> > > > +diff --git a/mk/gcc.mk b/mk/gcc.mk
> > > > +index adc77a24..81bfa78a 100644
> > > > +--- a/mk/gcc.mk
> > > > ++++ b/mk/gcc.mk
> > > > +@@ -13,11 +13,11 @@ nostdinc$(sm)      := -nostdinc -isystem $(shell
> > > > $(CC$(sm)) \
> > > > +                       -print-file-name=include 2> /dev/null)
> > > > +
> > > > + # Get location of libgcc from gcc
> > > > +-libgcc$(sm)   := $(shell $(CC$(sm)) $(CFLAGS$(arch-bits-$(sm))) \
> > > > ++libgcc$(sm)   := $(shell $(CC$(sm)) $(LIBGCC_LOCATE_CFLAGS)
> > > > $(CFLAGS$(arch-bits-$(sm))) \
> > > > +                       -print-libgcc-file-name 2> /dev/null)
> > > > +-libstdc++$(sm)        := $(shell $(CXX$(sm))
> > > > $(CXXFLAGS$(arch-bits-$(sm))) $(comp-cxxflags$(sm)) \
> > > > ++libstdc++$(sm)        := $(shell $(CXX$(sm))
> $(LIBGCC_LOCATE_CFLAGS)
> > > > $(CXXFLAGS$(arch-bits-$(sm))) $(comp-cxxflags$(sm)) \
> > > > +                       -print-file-name=libstdc++.a 2> /dev/null)
> > > > +-libgcc_eh$(sm)        := $(shell $(CXX$(sm))
> > > > $(CXXFLAGS$(arch-bits-$(sm))) $(comp-cxxflags$(sm)) \
> > > > ++libgcc_eh$(sm)        := $(shell $(CXX$(sm))
> $(LIBGCC_LOCATE_CFLAGS)
> > > > $(CXXFLAGS$(arch-bits-$(sm))) $(comp-cxxflags$(sm)) \
> > > > +                       -print-file-name=libgcc_eh.a 2> /dev/null)
> > > > +
> > > > + # Define these to something to discover accidental use
> > > > diff --git a/recipes-security/optee/optee-os_%.bbappend
> > > > b/recipes-security/optee/optee-os_%.bbappend
> > > > index 751dc3d0..e8af0124 100644
> > > > --- a/recipes-security/optee/optee-os_%.bbappend
> > > > +++ b/recipes-security/optee/optee-os_%.bbappend
> > > > @@ -1,6 +1,10 @@
> > > > +FILESEXTRAPATHS_prepend_ti-soc := "${THISDIR}/${PN}:"
> > > > +
> > > >  PV_ti-soc = "3.19.0+git${SRCPV}"
> > > >  SRCREV_ti-soc = "d6c5d0037b46f46caf71d67d7825d4b722cbcddf"
> > > > -SRC_URI_ti-soc = "git://
> github.com/OP-TEE/optee_os.git;protocol=https"
> > > > +SRC_URI_ti-soc = "git://
> github.com/OP-TEE/optee_os.git;protocol=https \
> > > > +    file://0006-allow-setting-sysroot-for-libgcc-lookup.patch \
> > > > +"
> > > >
> > > >  DEPENDS_append_ti-soc = " python3-cryptography-native"
> > > >
> > > > --
> > > > 2.38.2
>
Jose Quaresma Jan. 13, 2023, 4:52 p.m. UTC | #9 
Should meta-ti build also with OE default toolchain and without meta-arago
or not?

Jose

Jose Quaresma via lists.yoctoproject.org <quaresma.jose=
gmail.com@lists.yoctoproject.org> escreveu no dia quarta, 11/01/2023 à(s)
10:13:

>
>
> Denys Dmytriyenko <denis@denix.org> escreveu no dia terça, 10/01/2023
> à(s) 23:39:
>
>> Ok, this is not specific to the host OS.
>>
>> It is toolchain-specific though - it doesn't fail with the external Arm
>> toolchain, but fails with the toolchain built by OE, i.e. Poky, etc.
>>
>
> So this can be the reason to build with meta-arago and not without it.
> Thanks for looking at this.
>
> Jose
>
>
>>
>> On Wed, Jan 04, 2023 at 03:54:05PM -0500, Denys Dmytriyenko wrote:
>> > Not being able to reproduce the issue here:
>> >
>> > $ MACHINE=am64xx-evm bitbake optee-os
>> >
>> > Builds just fine.
>> >
>> > Any more pointers - host OS/version, etc? I'm building Dunfell in
>> Ubuntu 18.04
>> > container, but can try a newer one if that's the culprit.
>> >
>> >
>> > On Wed, Jan 04, 2023 at 07:18:50PM +0000, Jose Quaresma wrote:
>> > > Friendly ping :)
>> > >
>> > > thanks
>> > >
>> > > Jose Quaresma via lists.yoctoproject.org <quaresma.jose=
>> > > gmail.com@lists.yoctoproject.org> escreveu no dia terça, 13/12/2022
>> à(s)
>> > > 18:38:
>> > >
>> > > > f8182afd optee: Upgrade to upstream 3.17.0
>> > > > removes this patch but this is still required
>> > > >
>> > > > Currently building with am62xx-evm/am64xx-evm machine fails with:
>> > > >
>> > > > | aarch64-poky-linux-ld.bfd: cannot find libgcc.a: No such file or
>> > > > directory
>> > > > | make: *** [ldelf/link.mk:60: out/arm-plat-k3/ldelf/ldelf.elf]
>> Error 1
>> > > > | make: *** Waiting for unfinished jobs....
>> > > >
>> > > > Signed-off-by: Jose Quaresma <jose.quaresma@foundries.io>
>> > > > ---
>> > > >  ...ow-setting-sysroot-for-libgcc-lookup.patch | 34
>> +++++++++++++++++++
>> > > >  recipes-security/optee/optee-os_%.bbappend    |  6 +++-
>> > > >  2 files changed, 39 insertions(+), 1 deletion(-)
>> > > >  create mode 100644
>> > > >
>> recipes-security/optee/optee-os/0006-allow-setting-sysroot-for-libgcc-lookup.patch
>> > > >
>> > > > diff --git
>> > > >
>> a/recipes-security/optee/optee-os/0006-allow-setting-sysroot-for-libgcc-lookup.patch
>> > > >
>> b/recipes-security/optee/optee-os/0006-allow-setting-sysroot-for-libgcc-lookup.patch
>> > > > new file mode 100644
>> > > > index 00000000..17005396
>> > > > --- /dev/null
>> > > > +++
>> > > >
>> b/recipes-security/optee/optee-os/0006-allow-setting-sysroot-for-libgcc-lookup.patch
>> > > > @@ -0,0 +1,34 @@
>> > > > +From 0bab935695ebcf0c533b49896ab18ff33d4a47d1 Mon Sep 17 00:00:00
>> 2001
>> > > > +From: Ross Burton <ross.burton@arm.com>
>> > > > +Date: Tue, 26 May 2020 14:38:02 -0500
>> > > > +Subject: [PATCH] allow setting sysroot for libgcc lookup
>> > > > +
>> > > > +Explicitly pass the new variable LIBGCC_LOCATE_CFLAGS variable when
>> > > > searching
>> > > > +for the compiler libraries as there's no easy way to reliably pass
>> > > > --sysroot
>> > > > +otherwise.
>> > > > +
>> > > > +Upstream-Status: Pending [
>> https://github.com/OP-TEE/optee_os/issues/4188]
>> > > > +Signed-off-by: Ross Burton <ross.burton@arm.com>
>> > > > +---
>> > > > + mk/gcc.mk | 6 +++---
>> > > > + 1 file changed, 3 insertions(+), 3 deletions(-)
>> > > > +
>> > > > +diff --git a/mk/gcc.mk b/mk/gcc.mk
>> > > > +index adc77a24..81bfa78a 100644
>> > > > +--- a/mk/gcc.mk
>> > > > ++++ b/mk/gcc.mk
>> > > > +@@ -13,11 +13,11 @@ nostdinc$(sm)      := -nostdinc -isystem
>> $(shell
>> > > > $(CC$(sm)) \
>> > > > +                       -print-file-name=include 2> /dev/null)
>> > > > +
>> > > > + # Get location of libgcc from gcc
>> > > > +-libgcc$(sm)   := $(shell $(CC$(sm)) $(CFLAGS$(arch-bits-$(sm))) \
>> > > > ++libgcc$(sm)   := $(shell $(CC$(sm)) $(LIBGCC_LOCATE_CFLAGS)
>> > > > $(CFLAGS$(arch-bits-$(sm))) \
>> > > > +                       -print-libgcc-file-name 2> /dev/null)
>> > > > +-libstdc++$(sm)        := $(shell $(CXX$(sm))
>> > > > $(CXXFLAGS$(arch-bits-$(sm))) $(comp-cxxflags$(sm)) \
>> > > > ++libstdc++$(sm)        := $(shell $(CXX$(sm))
>> $(LIBGCC_LOCATE_CFLAGS)
>> > > > $(CXXFLAGS$(arch-bits-$(sm))) $(comp-cxxflags$(sm)) \
>> > > > +                       -print-file-name=libstdc++.a 2> /dev/null)
>> > > > +-libgcc_eh$(sm)        := $(shell $(CXX$(sm))
>> > > > $(CXXFLAGS$(arch-bits-$(sm))) $(comp-cxxflags$(sm)) \
>> > > > ++libgcc_eh$(sm)        := $(shell $(CXX$(sm))
>> $(LIBGCC_LOCATE_CFLAGS)
>> > > > $(CXXFLAGS$(arch-bits-$(sm))) $(comp-cxxflags$(sm)) \
>> > > > +                       -print-file-name=libgcc_eh.a 2> /dev/null)
>> > > > +
>> > > > + # Define these to something to discover accidental use
>> > > > diff --git a/recipes-security/optee/optee-os_%.bbappend
>> > > > b/recipes-security/optee/optee-os_%.bbappend
>> > > > index 751dc3d0..e8af0124 100644
>> > > > --- a/recipes-security/optee/optee-os_%.bbappend
>> > > > +++ b/recipes-security/optee/optee-os_%.bbappend
>> > > > @@ -1,6 +1,10 @@
>> > > > +FILESEXTRAPATHS_prepend_ti-soc := "${THISDIR}/${PN}:"
>> > > > +
>> > > >  PV_ti-soc = "3.19.0+git${SRCPV}"
>> > > >  SRCREV_ti-soc = "d6c5d0037b46f46caf71d67d7825d4b722cbcddf"
>> > > > -SRC_URI_ti-soc = "git://
>> github.com/OP-TEE/optee_os.git;protocol=https"
>> > > > +SRC_URI_ti-soc = "git://
>> github.com/OP-TEE/optee_os.git;protocol=https \
>> > > > +    file://0006-allow-setting-sysroot-for-libgcc-lookup.patch \
>> > > > +"
>> > > >
>> > > >  DEPENDS_append_ti-soc = " python3-cryptography-native"
>> > > >
>> > > > --
>> > > > 2.38.2
>>
>
>
> --
> Best regards,
>
> José Quaresma
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#15546):
> https://lists.yoctoproject.org/g/meta-ti/message/15546
> Mute This Topic: https://lists.yoctoproject.org/mt/96057453/5052612
> Group Owner: meta-ti+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub [
> quaresma.jose@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>
diff mbox series

Patch

diff --git a/conf/machine/include/k3.inc b/conf/machine/include/k3.inc
index 349f4fda..ef4f107f 100644
--- a/conf/machine/include/k3.inc
+++ b/conf/machine/include/k3.inc
@@ -15,7 +15,7 @@  PREFERRED_PROVIDER_virtual/bootloader = "u-boot-ti-staging"
 PREFERRED_PROVIDER_u-boot = "u-boot-ti-staging"
 
 KERNEL_IMAGETYPE = "Image"
-KERNEL_IMAGETYPES = "Image fitImage"
+KERNEL_IMAGETYPES = "Image"
 
 UBOOT_ARCH = "arm"
 UBOOT_ENTRYPOINT = "0x80008000"