From: "Rebecca Cran" <rebecca@bsdio.com>
To: devel@edk2.groups.io, Bob Feng <bob.c.feng@intel.com>,
Liming Gao <gaoliming@byosoft.com.cn>,
Yuwei Chen <yuwei.chen@intel.com>,
Sean Brogan <sean.brogan@microsoft.com>,
Sami Mujawar <sami.mujawar@arm.com>,
Leif Lindholm <leif@nuviainc.com>,
Ard Biesheuvel <ardb+tianocore@kernel.org>
Subject: Re: [edk2-devel] [PATCH 0/2] BaseTools: Switch ARM/AARCH64 CI gcc from Linaro to Arm
Date: Thu, 26 Aug 2021 15:02:55 -0600 [thread overview]
Message-ID: <4be6fd6e-b468-d00e-3665-fb94d169633d@bsdio.com> (raw)
In-Reply-To: <169DD8C33F04384D.18298@groups.io>
I've created a ticket in Bugzilla:
https://bugzilla.tianocore.org/show_bug.cgi?id=3594.
--
Rebecca Cran
On 8/22/21 11:35 PM, Rebecca Cran wrote:
> Linaro no longer do gcc releases - Arm creates them now.
>
> Update the gcc_[arm,aarch64]_linux_ext_dep.yaml files in BaseTools/Bin to
> switch from Linaro's old release to the latest gcc 10.3-2021.07 release
> from Arm.
>
> The private PR https://github.com/tianocore/edk2/pull/1909 failed due to
> a problem with GCC5_[ARM,AARCH64]_PREFIX. I don't know if there are more
> changes I need to add, or if it's a problem with the CI system.
>
> Rebecca Cran (2):
> BaseTools: Switch to downloading the ARM compiler from Arm's site
> BaseTools: Switch to downloading the AARCH64 compiler from Arm's site
>
> BaseTools/Bin/gcc_aarch64_linux_ext_dep.yaml | 10 +++++-----
> BaseTools/Bin/gcc_arm_linux_ext_dep.yaml | 10 +++++-----
> 2 files changed, 10 insertions(+), 10 deletions(-)
>
next parent reply other threads:[~2021-08-26 21:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <169DD8C33F04384D.18298@groups.io>
2021-08-26 21:02 ` Rebecca Cran [this message]
2021-08-27 13:31 ` [edk2-devel] [PATCH 0/2] BaseTools: Switch ARM/AARCH64 CI gcc from Linaro to Arm Ard Biesheuvel
2021-08-28 1:16 ` Rebecca Cran
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-list 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=4be6fd6e-b468-d00e-3665-fb94d169633d@bsdio.com \
--to=devel@edk2.groups.io \
/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