public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "丰立波 via groups.io" <lbfeng=kunluntech.com.cn@groups.io>
To: devel  <devel@edk2.groups.io>
Subject: Re: [edk2-devel] buiding Uefi Universal Payload failed
Date: Thu, 13 Mar 2025 17:26:03 +0800 (GMT+08:00)	[thread overview]
Message-ID: <ACgAfwCvLhGLkwe0zJlFWqqM.2.1741857963364.Hmail.lbfeng@kunluntech.com.cn> (raw)
In-Reply-To: <182C50338DEC62BE.19915@groups.io>


[-- Attachment #1.1: Type: text/plain, Size: 2442 bytes --]

Hello,


Clang tool chains is said better in dealing 32bit mode and 64bit mode, and generating elf file. So UniversalPayloadEntry must be built using Clang tool chains (I think this is done by the hardcode "PayloadEntryToolChain = 'CLANGDWARF'" in UniversalPayloadBuild.py, ignoring the cmd line option -t <TOOLCHAINS>).


At the beginning, BaseTools/Scripts contains a ClangBase.lds file, as the below link shows, the file is a linker script. But now, the link script is missing. Without ClangBase.lds, building UniversalPayloadEnty failed. How can I get the ClangBase.lds? or Did I miss something when setting up the building enviroment? 



https://edk2.groups.io/g/devel/message/75955









Thanks


Best Regards


Feng Libo




Original:
From:丰立波 via groups.io<lbfeng=kunluntech.com.cn@groups.io>Date:2025-03-13 16:42:09(中国 (GMT+08:00))To:devel <devel@edk2.groups.io> , radio-fan <radio-fan@mail.ru>Cc:Subject:Re: [edk2-devel] buiding Uefi Universal Payload failedHello, Stepan,


Thanks for the reply.
You didn't encounter such problems, just because ClangBase.lds already exists in your directory BaseTools/Scripts, as your building log below. But ClangBase.lds is absent in my BaseTools/Scripts, there is only GccBase.lds. Where did you get the ClangBase.lds?







GccBase.lds claims it is "Unified linker script for GCC and CLANG based builds", so I duplicate one and change the file name to ClangBase.lds. Now, building is successful, but I am not sure it is the right way.


Best Regards


Feng Libo


Original:
From:Stepan via groups.io<radio-fan=mail.ru@groups.io>Date:2025-03-12 13:21:35(中国 (GMT+08:00))To:丰立波<lbfeng@kunluntech.com.cn> , devel<devel@edk2.groups.io>Cc:Subject:[edk2-devel] buiding Uefi Universal Payload failedHello Feng Libo,
 
1) Are You building BaseTools?
2) Are You source edksetup.sh?
 
We are use Ubuntu and GCC and we have not encountered such problems. Also You can check our topic about building universal payload. https://edk2.groups.io/g/devel/topic/universal_uefi_elf_payload/111543703











-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#121197): https://edk2.groups.io/g/devel/message/121197
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 #1.2: Type: text/html, Size: 11956 bytes --]

[-- Attachment #2: picture.png --]
[-- Type: image/png, Size: 83512 bytes --]

[-- Attachment #3: picture.png --]
[-- Type: image/png, Size: 60731 bytes --]

  parent reply	other threads:[~2025-03-13  9:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-11  8:43 [edk2-devel] buiding Uefi Universal Payload failed 丰立波 via groups.io
2025-03-12  5:21 ` 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 [this message]
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
2025-03-29  2:50         ` 丰立波 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=ACgAfwCvLhGLkwe0zJlFWqqM.2.1741857963364.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