From: "Gerd Hoffmann" <kraxel@redhat.com>
To: Rebecca Cran <rebecca@bsdio.com>
Cc: devel@edk2.groups.io, "Liming Gao" <gaoliming@byosoft.com.cn>,
"Bob Feng" <bob.c.feng@intel.com>,
"Yuwei Chen" <yuwei.chen@intel.com>,
"Michael D Kinney" <michael.d.kinney@intel.com>,
"Michael Kubacki" <mikuback@linux.microsoft.com>,
"Sean Brogan" <sean.brogan@microsoft.com>,
"Chasel Chiu" <chasel.chiu@intel.com>,
"Nate DeSimone" <nathaniel.l.desimone@intel.com>,
"Star Zeng" <star.zeng@intel.com>,
"Andrew Fish" <afish@apple.com>, "Ray Ni" <ray.ni@intel.com>,
"Leif Lindholm" <quic_llindhol@quicinc.com>,
"Zhiguang Liu" <zhiguang.liu@intel.com>,
"Jian J Wang" <jian.j.wang@intel.com>,
"Xiaoyu Lu" <xiaoyu1.lu@intel.com>,
"Guomin Jiang" <guomin.jiang@intel.com>,
"Gua Guo" <gua.guo@intel.com>, "Ard Biesheuvel" <ardb@kernel.org>,
"Pedro Falcato" <pedro.falcato@gmail.com>,
"Marvin Häuser" <mhaeuser@posteo.de>
Subject: Re: [PATCH v3 09/13] BaseTools/Conf/tools_def.template: Add GCC and GCCNOLTO toolchains
Date: Mon, 17 Apr 2023 13:03:37 +0200 [thread overview]
Message-ID: <ealsvunr6wzdrkgfoubbjfwzkzetv3y4eii3fwh6oh553cxdnc@6bswwtb5rmb7> (raw)
In-Reply-To: <20230416170532.278338-10-rebecca@bsdio.com>
> +DEFINE GCCNOLTO_IA32_PREFIX = ENV(GCCNOLTO_BIN)
> +DEFINE GCCNOLTO_X64_PREFIX = ENV(GCCNOLTO_BIN)
> +
> DEFINE GCC5_IA32_PREFIX = ENV(GCC5_BIN)
> DEFINE GCC5_X64_PREFIX = ENV(GCC5_BIN)
> +DEFINE GCC_IA32_PREFIX = ENV(GCC_BIN)
> +DEFINE GCC_X64_PREFIX = ENV(GCC_BIN)
Does it make sense to have a separate prefix for each gcc variant?
I guess it makes sense for the existing GCC5 and GCC4x configs for
backward compatibility reasons, but for the new GCC / GCCNOLTO variants
not so much.
Trying to build ia32 ovmf with clang (15) and openssl fails btw:
ld.lld: error: undefined symbol: __lshrdi3
But I guess that isn't something new introduced by this series.
take care,
Gerd
next prev parent reply other threads:[~2023-04-17 11:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-16 17:05 [PATCH v3 00/13] BaseTools,CryptoPkg,EmulatorPkg,MdePkg,others: Delete CLANG35,CLANG38,VS2008-2013,EBC, deprecate GCC48,GCC49,GCC5, add GCC and GCCNOLTO, update CLANGDWARF Rebecca Cran
2023-04-16 17:05 ` [PATCH v3 01/13] BaseTools,CryptoPkg: Update CLANGDWARF, remove CLANG 35/38 toolchains Rebecca Cran
2023-04-16 17:05 ` [PATCH v3 02/13] BaseTools: Remove VS2008, 2010, 2012 and 2013 toolchain definitions Rebecca Cran
2023-04-16 17:05 ` [PATCH v3 03/13] BaseTools: Remove VS2008-VS2013 remnants Rebecca Cran
2023-04-16 17:05 ` [PATCH v3 04/13] MdePkg: " Rebecca Cran
2023-04-16 17:05 ` [PATCH v3 05/13] edksetup.bat: " Rebecca Cran
2023-04-16 17:05 ` [PATCH v3 06/13] BaseTools: Remove unused IPHONE_TOOLS and SOURCERY_CYGWIN_TOOLS defs Rebecca Cran
2023-04-16 17:05 ` [PATCH v3 07/13] BaseTools: Remove EBC (EFI Byte Code) compiler definitions Rebecca Cran
2023-04-16 17:05 ` [PATCH v3 08/13] BaseTools: Update VS toolchain descriptions in tools_def.txt.template Rebecca Cran
2023-04-16 17:05 ` [PATCH v3 09/13] BaseTools/Conf/tools_def.template: Add GCC and GCCNOLTO toolchains Rebecca Cran
2023-04-17 11:03 ` Gerd Hoffmann [this message]
2023-04-17 14:26 ` Rebecca Cran
2023-04-16 17:05 ` [PATCH v3 10/13] BaseTools: Only call LoadConfiguration once in build.py Rebecca Cran
2023-04-16 17:05 ` [PATCH v3 11/13] BaseTools: Add a deprecation warning for GCC48,GCC49,GCC5 to build.py Rebecca Cran
2023-04-16 17:05 ` [PATCH v3 12/13] BaseTools/Conf/tools_def.template: Add section for deprecated toolchains Rebecca Cran
2023-04-16 17:05 ` [PATCH v3 13/13] BaseTools/Conf/tools_def.template: Bump VERSION to 3.00 Rebecca Cran
2023-04-17 11:32 ` [PATCH v3 00/13] BaseTools,CryptoPkg,EmulatorPkg,MdePkg,others: Delete CLANG35,CLANG38,VS2008-2013,EBC, deprecate GCC48,GCC49,GCC5, add GCC and GCCNOLTO, update CLANGDWARF Gerd Hoffmann
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=ealsvunr6wzdrkgfoubbjfwzkzetv3y4eii3fwh6oh553cxdnc@6bswwtb5rmb7 \
--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