From: "丰立波 via groups.io" <lbfeng=kunluntech.com.cn@groups.io>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: [edk2-devel] buiding Uefi Universal Payload failed
Date: Tue, 11 Mar 2025 16:43:49 +0800 (GMT+08:00) [thread overview]
Message-ID: <AF2AFQAZLpWH9lm1mgGT0ao7.1.1741682629533.Hmail.lbfeng@kunluntech.com.cn> (raw)
[-- Attachment #1: Type: text/plain, Size: 1442 bytes --]
Hello,
I am building Uefi Universal payload with the below python script,
python UefiPayloadPkg/UniversalPayloadBuild.py -t GCC5, or python UefiPayloadPkg/UniversalPayloadBuild.py -t CLANGDWARF
a building error always reports, no matter the toolchain is assigned GCC5 or CLANGDWARF.
ld.lld: error: cannot find linker script /home/EDKII/edk2/BaseTools/Scripts/ClangBase.lds
Did I miss something when setup the building enviroment?
Now, I changed CLANGDWARF to GCC5 in python script UefiPayloadPkg/UniversalPayloadBuild.py, and only with python UefiPayloadPkg/UniversalPayloadBuild.py -t GCC5, building is successful.
if Args.Fit == True:
PayloadEntryToolChain = ToolChain
Args.Macro.append("UNIVERSAL_PAYLOAD_FORMAT=FIT")
UpldEntryFile = "FitUniversalPayloadEntry"
else:
PayloadEntryToolChain = 'CLANGDWARF' <======== GCC5
Args.Macro.append("UNIVERSAL_PAYLOAD_FORMAT=ELF")
UpldEntryFile = "UniversalPayloadEntry"
the building enviroment is Ubuntu 22.04, GCC 11.4.0, clang 14.0.0.
Best Regards
Feng Libo
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#121183): https://edk2.groups.io/g/devel/message/121183
Mute This Topic: https://groups.io/mt/111636381/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
[-- Attachment #2: Type: text/html, Size: 5257 bytes --]
next reply other threads:[~2025-03-11 8:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 8:43 丰立波 via groups.io [this message]
2025-03-12 5:21 ` [edk2-devel] buiding Uefi Universal Payload failed Stepan via groups.io
2025-03-13 8:42 ` 丰立波 via groups.io
2025-03-13 10:35 ` Alireza Banejad via groups.io
[not found] ` <182C50338DEC62BE.19915@groups.io>
2025-03-13 9:26 ` 丰立波 via groups.io
2025-03-13 10:53 ` Stepan via groups.io
2025-03-13 12:05 ` Ard Biesheuvel via groups.io
2025-03-18 8:19 ` Stepan via groups.io
2025-03-18 8:20 ` Stepan via groups.io
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=AF2AFQAZLpWH9lm1mgGT0ao7.1.1741682629533.Hmail.lbfeng@kunluntech.com.cn \
--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