From: "Gerd Hoffmann" <kraxel@redhat.com>
To: devel@edk2.groups.io, lichao@loongson.cn
Cc: maobibo@loongson.cn, "WANG Xuerui" <i.qemu@xen0n.name>,
qemu-devel <qemu-devel@nongnu.org>,
"Song Gao" <gaosong@loongson.cn>, 杨小娟 <yangxiaojuan@loongson.cn>
Subject: Re: [edk2-devel] On integrating LoongArch EDK2 firmware into QEMU build process
Date: Mon, 3 Apr 2023 12:58:37 +0200 [thread overview]
Message-ID: <bdo2agsoacxe26lb5d5kyo7mqhwacilnrpn2buhocgg2lv3o2d@gdowo5nfzpop> (raw)
In-Reply-To: <aa56f4de-e50e-7a7f-3e0e-39e5fa20df29@loongson.cn>
On Mon, Apr 03, 2023 at 06:13:41PM +0800, Chao Li wrote:
> Hi Bibo,
>
> gcc-13 will support this new feature, so we expect this issue to be resolved
> when using gcc-13, which may be released at this month.
>
> If Fedora38 does not plan to use gcc-13 now, I suggest that CI can download
> a LoongArch cross gcc-13 when creating a docker image, just like EDK2 CI
> process. You can refer following link for more information:
The non-cross gcc already is at 13. Fedora builds the distro with
pre-release gcc so gcc gets some serious real-world testing before
release.
The cross compilers lagging behind a bit, not sure whenever there is
some actual problem or whenever maintainers are just waiting for the
final gcc-13 release.
> https://github.com/tianocore/containers/blob/main/Fedora-37/Dockerfile .
> EDK2 CI uses Fedora35 and Fedora37 docker images for LoongArch, they will
> download a LoongArch cross gcc-13 when the CI targets is LoongArch.
While that works as temporary stopgap for edk2 CI it is a non-starter
for fedora distro builds. Any builds must be done using compilers
shipped by fedora. So, fedora shipping edk2-loongarch (or
ipxe-loongarch) packages is blocked by this.
> We are really sorry about that, I think this solution will make more work
> for you, but I think it is the best way for now, and I believe it will be
> solved when Fedora uses gcc-13 in the future.
I'll go just wait for gcc-13 cross compilers land in fedora then.
take care,
Gerd
prev parent reply other threads:[~2023-04-03 10:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1f1d3d9f-c3df-4f29-df66-886410994cc3@xen0n.name>
[not found] ` <67517424-0f32-09f8-6446-53f71ebd59b5@loongson.cn>
[not found] ` <x5vbhjcyc3jl5u3qdjg2dq2znwhdq7ordmbjm6s2hftwyusqp2@r6smasorrjor>
[not found] ` <317e3008-e2bd-8af6-2cf5-dad49d98cb8d@loongson.cn>
2023-04-03 8:51 ` On integrating LoongArch EDK2 firmware into QEMU build process maobibo
2023-04-03 10:13 ` [edk2-devel] " Chao Li
2023-04-03 10:29 ` Michael Brown
2023-04-03 11:04 ` Gerd Hoffmann
2023-04-04 2:24 ` Chao Li
2023-04-03 10:58 ` Gerd Hoffmann [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-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=bdo2agsoacxe26lb5d5kyo7mqhwacilnrpn2buhocgg2lv3o2d@gdowo5nfzpop \
--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