From: Denys Dmytriyenko <denis@denix.org>
To: Ross Burton <ross.burton@arm.com>
Cc: Michael Lynch <mlynch@hi-techniques.com>,
"meta-arm@lists.yoctoproject.org"
<meta-arm@lists.yoctoproject.org>,
meta-ti@lists.yoctoproject.org
Subject: Re: [meta-ti] [meta-arm] optee failing to build on head of dunfell branch for j7-evm
Date: Mon, 22 Jan 2024 15:04:47 -0500 [thread overview]
Message-ID: <20240122200447.GG18608@denix.org> (raw)
In-Reply-To: <17ACBF07F3A964F3.17265@lists.yoctoproject.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
prev parent reply other threads:[~2024-01-22 20:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <UuhE.1705687266596590169.nYL6@lists.yoctoproject.org>
[not found] ` <EF84BE17-CEE6-45A8-9FCC-0CDD4BB6F111@arm.com>
[not found] ` <CADSA=uHnkpYGXfiK-u5NkHgqLutFh=Fy75Uurv4Zw7HcAMqCcg@mail.gmail.com>
[not found] ` <797DCC01-1255-43F0-9596-85E7F173A6F0@arm.com>
[not found] ` <CADSA=uFgpA6E=m2XvGuu-oSG+_BcXbGz04=Hf2bpN0vVN4=SgQ@mail.gmail.com>
[not found] ` <2EB56308-5017-42DE-B55F-92AF772AE1E2@arm.com>
2024-01-22 18:33 ` [meta-arm] optee failing to build on head of dunfell branch for j7-evm Denys Dmytriyenko
[not found] ` <17ACBF07F3A964F3.17265@lists.yoctoproject.org>
2024-01-22 20:04 ` Denys Dmytriyenko [this message]
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=20240122200447.GG18608@denix.org \
--to=denis@denix.org \
--cc=meta-arm@lists.yoctoproject.org \
--cc=meta-ti@lists.yoctoproject.org \
--cc=mlynch@hi-techniques.com \
--cc=ross.burton@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).