Re: [meta-ti] [meta-arm] optee failing to build on head of dunfell branch for j7-evm

[Denys Dmytriyenko <denis@denix.org>]

On Mon, Jan 22, 2024 at 01:33:12PM -0500, Denys Dmytriyenko wrote:
> On Mon, Jan 22, 2024 at 02:25:34PM +0000, Ross Burton wrote:
> > On 22 Jan 2024, at 14:11, Michael Lynch <mlynch@hi-techniques.com> wrote:
> > > 
> > > Meta-ti branch is head of dunfell.
> > > 
> > > Ok I believe see what's going on.  The dunfell branch of the meta-ti layer 
> > > appends optee_os such that it updates optee_os to the 3.20.0 git version 
> > > but does NOT supply a replacement patch file that works with the 
> > > "mk/gcc.mk" file that comes with 3.20.0 nor does TI's optee_os append 
> > > override do_patch and I believe this is why the build ends up failing?  
> > > Maybe time to ask on the meta-ti forum?
> > 
> > Absolutely.  They don’t appear to be testing that combination.
> 
> Well, TI historically have been using stable/LTS releases even for adding new 
> platforms, hence bumping BSP components to newer versions, often backporting 
> them from master, but sometimes even updating OPTEE/TFA before meta-arm does. 
> Those combinations are always being tested for TI platforms, as overrides in 
> those bbappends are specific to TI SoC platforms.
> 
> Now, the issue is with the libgcc sysroot patch that's been there forever, 
> until just several days ago when it got replaced with CFLAGS in master. And 
> passing sysroot is required for OE-built toolchain.
> 
> Anyway, I've done some digging - in the past TI was using external toolchain 
> for their products, so when optee-os got bumped to 3.20, the issue with the 
> patch was missed, as external toolchain has no issue finding libgcc, e.g.:
> 
> TCMODE = "external-arm"
> EXTERNAL_TOOLCHAIN = "<path-to-the-toolchain>"
> 
> And switching TI products to OE-built toolchain (TOOLCHAIN_TYPE=internal) 
> surely exposes this issue:
> 
> | aarch64-oe-linux-ld.bfd: cannot find libgcc.a: No such file or directory
> 
> TI products have switched to Kirkstone about a year ago and also changed the 
> default toolchain to OE-built one, so no issues there or in master.
> 
> And Dunfell branch hasn't seen any updates in meta-ti since then, but I guess 
> this can be fixed, as apparently there are people still using Dunfell...

https://patchwork.yoctoproject.org/project/ti/patch/20240122191902.1561510-1-denis@denix.org/

-- 
Denys