From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from aws-us-west-2-korg-lkml-1.web.codeaurora.org (localhost.localdomain [127.0.0.1]) by smtp.lore.kernel.org (Postfix) with ESMTP id B8DA4C47DD9 for ; Mon, 22 Jan 2024 18:33:24 +0000 (UTC) Received: from mailout4.zoneedit.com (mailout4.zoneedit.com [64.68.198.64]) by mx.groups.io with SMTP id smtpd.web11.759.1705948398226059331 for ; Mon, 22 Jan 2024 10:33:19 -0800 Authentication-Results: mx.groups.io; dkim=none (message not signed); spf=pass (domain: denix.org, ip: 64.68.198.64, mailfrom: denis@denix.org) Received: from localhost (localhost [127.0.0.1]) by mailout4.zoneedit.com (Postfix) with ESMTP id E4AA340C2E; Mon, 22 Jan 2024 18:33:16 +0000 (UTC) Received: from mailout4.zoneedit.com ([127.0.0.1]) by localhost (zmo14-pco.easydns.vpn [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dTDR-8xvSsxe; Mon, 22 Jan 2024 18:33:16 +0000 (UTC) Received: from mail.denix.org (pool-100-15-87-159.washdc.fios.verizon.net [100.15.87.159]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout4.zoneedit.com (Postfix) with ESMTPSA id B3CE640BE6; Mon, 22 Jan 2024 18:33:13 +0000 (UTC) Received: by mail.denix.org (Postfix, from userid 1000) id EA44B163DDD; Mon, 22 Jan 2024 13:33:12 -0500 (EST) Date: Mon, 22 Jan 2024 13:33:12 -0500 From: Denys Dmytriyenko To: Ross Burton Cc: Michael Lynch , "meta-arm@lists.yoctoproject.org" , meta-ti@lists.yoctoproject.org Subject: Re: [meta-arm] optee failing to build on head of dunfell branch for j7-evm Message-ID: <20240122183312.GF18608@denix.org> References: <797DCC01-1255-43F0-9596-85E7F173A6F0@arm.com> <2EB56308-5017-42DE-B55F-92AF772AE1E2@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <2EB56308-5017-42DE-B55F-92AF772AE1E2@arm.com> User-Agent: Mutt/1.5.20 (2009-06-14) Content-Transfer-Encoding: quoted-printable List-Id: X-Webhook-Received: from li982-79.members.linode.com [45.33.32.79] by aws-us-west-2-korg-lkml-1.web.codeaurora.org with HTTPS for ; Mon, 22 Jan 2024 18:33:24 -0000 X-Groupsio-URL: https://lists.yoctoproject.org/g/meta-arm/message/5352 On Mon, Jan 22, 2024 at 02:25:34PM +0000, Ross Burton wrote: > On 22 Jan 2024, at 14:11, Michael Lynch wrot= e: > >=20 > > Meta-ti branch is head of dunfell. > >=20 > > Ok I believe see what's going on. The dunfell branch of the meta-ti = layer=20 > > appends optee_os such that it updates optee_os to the 3.20.0 git vers= ion=20 > > but does NOT supply a replacement patch file that works with the=20 > > "mk/gcc.mk" file that comes with 3.20.0 nor does TI's optee_os append= =20 > > override do_patch and I believe this is why the build ends up failing= ? =20 > > Maybe time to ask on the meta-ti forum? >=20 > Absolutely. They don=E2=80=99t appear to be testing that combination. Well, TI historically have been using stable/LTS releases even for adding= new=20 platforms, hence bumping BSP components to newer versions, often backport= ing=20 them from master, but sometimes even updating OPTEE/TFA before meta-arm d= oes.=20 Those combinations are always being tested for TI platforms, as overrides= in=20 those bbappends are specific to TI SoC platforms. Now, the issue is with the libgcc sysroot patch that's been there forever= ,=20 until just several days ago when it got replaced with CFLAGS in master. A= nd=20 passing sysroot is required for OE-built toolchain. Anyway, I've done some digging - in the past TI was using external toolch= ain=20 for their products, so when optee-os got bumped to 3.20, the issue with t= he=20 patch was missed, as external toolchain has no issue finding libgcc, e.g.= : TCMODE =3D "external-arm" EXTERNAL_TOOLCHAIN =3D "" And switching TI products to OE-built toolchain (TOOLCHAIN_TYPE=3Dinterna= l)=20 surely exposes this issue: | aarch64-oe-linux-ld.bfd: cannot find libgcc.a: No such file or director= y TI products have switched to Kirkstone about a year ago and also changed = the=20 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 g= uess=20 this can be fixed, as apparently there are people still using Dunfell... --=20 Denys