From: "Rebecca Cran" <rebecca@bsdio.com>
To: "Marvin Häuser" <mhaeuser@posteo.de>
Cc: devel@edk2.groups.io, patrick.rudolph@9elements.com,
guo.dong@intel.com, gua.guo@intel.com, james.lu@intel.com,
ray.ni@intel.com, ardb@kernel.org
Subject: Re: [edk2-devel] [PATCH 1/3] BaseTools/Conf/tools_def: Fix linking using CLANGDWARF_IA32
Date: Thu, 23 Mar 2023 08:43:21 -0600 [thread overview]
Message-ID: <9c522ce1-af51-7234-df72-a20b982d243b@bsdio.com> (raw)
In-Reply-To: <174D4F37D4EEDF26.23349@groups.io>
The linker problems I was seeing were unrelated to those Patrick's patch
fixed.
I just applied Patrick's changes on top of my CLANGDWARF patches and
OvmfPkgIa32.dsc builds fine.
--
Rebecca Cran
On 3/17/23 2:35 PM, Rebecca Cran wrote:
> Building with "build -p OvmfPkg/OvmfPkgX64.dsc -a X64 -t CLANGDWARF -b
> RELEASE" on FreeBSD causes the following errors:
>
>
> ld.lld: error: relocation R_X86_64_64 cannot be used against local
> symbol; recompile with -fPIC
> >>> defined in
> /home/bcran/src/uefi/edk2/Build/OvmfX64/RELEASE_CLANGDWARF/X64/UefiCpuPkg/Library/CpuExceptionHandlerLib/SecPeiCpuExceptionHandlerLib/OUTPUT/SecPeiCpuExceptionHandlerLib.lib(ExceptionHandlerAsm.obj)
> >>> referenced by
> /home/bcran/src/uefi/edk2/Build/OvmfX64/RELEASE_CLANGDWARF/X64/UefiCpuPkg/Library/CpuExceptionHandlerLib/SecPeiCpuExceptionHandlerLib/OUTPUT/X64/ExceptionHandlerAsm.iii
> >>> ExceptionHandlerAsm.obj:(.text+0x5) in archive
> /home/bcran/src/uefi/edk2/Build/OvmfX64/RELEASE_CLANGDWARF/X64/UefiCpuPkg/Library/CpuExceptionHandlerLib/SecPeiCpuExceptionHandlerLib/OUTPUT/SecPeiCpuExceptionHandlerLib.lib
>
> ld.lld: error: relocation R_X86_64_64 cannot be used against local
> symbol; recompile with -fPIC
> >>> defined in
> /home/bcran/src/uefi/edk2/Build/OvmfX64/RELEASE_CLANGDWARF/X64/UefiCpuPkg/Library/CpuExceptionHandlerLib/SecPeiCpuExceptionHandlerLib/OUTPUT/SecPeiCpuExceptionHandlerLib.lib(ExceptionHandlerAsm.obj)
> >>> referenced by
> /home/bcran/src/uefi/edk2/Build/OvmfX64/RELEASE_CLANGDWARF/X64/UefiCpuPkg/Library/CpuExceptionHandlerLib/SecPeiCpuExceptionHandlerLib/OUTPUT/X64/ExceptionHandlerAsm.iii
> >>> ExceptionHandlerAsm.obj:(.text+0x14) in archive
> /home/bcran/src/uefi/edk2/Build/OvmfX64/RELEASE_CLANGDWARF/X64/UefiCpuPkg/Library/CpuExceptionHandlerLib/SecPeiCpuExceptionHandlerLib/OUTPUT/SecPeiCpuExceptionHandlerLib.lib
>
> ld.lld: error: relocation R_X86_64_64 cannot be used against local
> symbol; recompile with -fPIC
> >>> defined in
> /home/bcran/src/uefi/edk2/Build/OvmfX64/RELEASE_CLANGDWARF/X64/UefiCpuPkg/Library/CpuExceptionHandlerLib/SecPeiCpuExceptionHandlerLib/OUTPUT/SecPeiCpuExceptionHandlerLib.lib(ExceptionHandlerAsm.obj)
> >>> referenced by
> /home/bcran/src/uefi/edk2/Build/OvmfX64/RELEASE_CLANGDWARF/X64/UefiCpuPkg/Library/CpuExceptionHandlerLib/SecPeiCpuExceptionHandlerLib/OUTPUT/X64/ExceptionHandlerAsm.iii
> >>> ExceptionHandlerAsm.obj:(.text+0x23) in archive
> /home/bcran/src/uefi/edk2/Build/OvmfX64/RELEASE_CLANGDWARF/X64/UefiCpuPkg/Library/CpuExceptionHandlerLib/SecPeiCpuExceptionHandlerLib/OUTPUT/SecPeiCpuExceptionHandlerLib.lib
>
>
> Thinking about it, it might actually be a problem with the FreeBSD
> system toolchain. On Linux, I get a different set of errors about
> redefining uint64_t etc.
>
>
next prev parent reply other threads:[~2023-03-23 14:43 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 14:06 [PATCH 1/3] BaseTools/Conf/tools_def: Fix linking using CLANGDWARF_IA32 Patrick Rudolph
2023-03-17 14:06 ` [PATCH 2/3] BaseTools/Conf/tools_def: Fix CLANGDWARF_IA32_X64 Patrick Rudolph
2023-03-26 19:39 ` [edk2-devel] " Sheng Lean Tan
[not found] ` <17500F66A352AD33.14179@groups.io>
2023-03-26 19:42 ` Sheng Lean Tan
2023-03-28 5:38 ` 回复: " gaoliming
2023-03-28 11:25 ` Marvin Häuser
2023-03-31 4:53 ` 回复: " gaoliming
2023-03-31 10:57 ` Marvin Häuser
2023-04-03 0:52 ` 回复: " gaoliming
2023-04-03 5:53 ` Patrick Rudolph
2023-03-31 14:41 ` Ni, Ray
2023-03-31 14:58 ` Marvin Häuser
2023-03-17 17:30 ` [edk2-devel] [PATCH 1/3] BaseTools/Conf/tools_def: Fix linking using CLANGDWARF_IA32 Rebecca Cran
2023-03-17 17:44 ` Marvin Häuser
2023-03-17 20:35 ` Rebecca Cran
[not found] ` <174D4F37D4EEDF26.23349@groups.io>
2023-03-23 14:43 ` Rebecca Cran [this message]
2023-03-23 14:51 ` Sheng Lean Tan
2023-03-26 19:35 ` Sheng Lean Tan
2023-03-28 5:42 ` 回复: " gaoliming
2023-03-30 7:30 ` Sheng Lean Tan
2023-03-30 8:04 ` Marvin Häuser
2023-03-30 9:47 ` Patrick Rudolph
2023-04-04 12:46 ` Sheng Lean Tan
2023-04-05 8:27 ` Sheng Lean Tan
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=9c522ce1-af51-7234-df72-a20b982d243b@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