From: "Ard Biesheuvel" <ardb@kernel.org>
To: Rebecca Cran <quic_rcran@quicinc.com>
Cc: edk2-devel-groups-io <devel@edk2.groups.io>,
Ard Biesheuvel <ardb+tianocore@kernel.org>,
Jiewen Yao <jiewen.yao@intel.com>,
Jordan Justen <jordan.l.justen@intel.com>,
Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: OvmfPkgX64 doesn't build with CLANG38 (clang 14.0.3) NOOPT - undefined reference to `memcpy'
Date: Wed, 25 May 2022 17:50:17 +0200 [thread overview]
Message-ID: <CAMj1kXFsQNmYbAHZ5vnp3kP_q2P98cjKSaEn+55Q7vLC2KaF1g@mail.gmail.com> (raw)
In-Reply-To: <19fda580-50da-302b-4c4e-0457fb28174b@quicinc.com>
On Wed, 25 May 2022 at 17:08, Rebecca Cran <quic_rcran@quicinc.com> wrote:
>
> I noticed OvmfPkg/OvmfPkgX64.dsc doesn't build with `-t CLANG38 -b
> NOOPT` (with clang version 14.0.2) with the latest edk2 master
> (07c0c2eb0a5970db614ebce1060fc79d6904bdfd):
>
> make: Nothing to be done for 'tbuild'.
> /usr/bin/ld: /usr/bin/ld: DWARF error: invalid or unhandled FORM value:
> 0x23
> /home/bcran/src/upstream/uefi/edk2/Build/OvmfX64/NOOPT_CLANG38/X64/OvmfPkg/VirtioGpuDxe/VirtioGpu/OUTPUT/VirtioGpuDxe.lib(Gop.obj):
> in function `GopSetMode':
> Gop.c:(.text.GopSetMode+0x418): undefined reference to `memcpy'
Can you dump the object file to see where the memcpy() call is emitted?
> Building ...
> /home/bcran/src/upstream/uefi/edk2/OvmfPkg/PlatformPei/PlatformPei.inf
> [X64]
> clang-14.0: error: linker command failed with exit code 1 (use -v to see
> invocation)
> make: Nothing to be done for 'tbuild'.
> make: *** [GNUmakefile:358:
> /home/bcran/src/upstream/uefi/edk2/Build/OvmfX64/NOOPT_CLANG38/X64/OvmfPkg/VirtioGpuDxe/VirtioGpu/DEBUG/VirtioGpuDxe.dll]
> Error 1
>
>
> build.py...
> : error 7000: Failed to execute command
> make tbuild
> [/home/bcran/src/upstream/uefi/edk2/Build/OvmfX64/NOOPT_CLANG38/X64/OvmfPkg/VirtioGpuDxe/VirtioGpu]
>
>
> build.py...
> : error F002: Failed to build module
> /home/bcran/src/upstream/uefi/edk2/OvmfPkg/VirtioGpuDxe/VirtioGpu.inf [X64, CLANG38, NOOPT]
>
> - Failed -
> Build end time: 09:03:38, May.25 2022
> Build total time: 00:00:07
>
>
> --
> Rebecca Cran
next prev parent reply other threads:[~2022-05-25 15:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 15:08 OvmfPkgX64 doesn't build with CLANG38 (clang 14.0.3) NOOPT - undefined reference to `memcpy' Rebecca Cran
2022-05-25 15:50 ` Ard Biesheuvel [this message]
2022-05-25 16:43 ` [edk2-devel] " Pedro Falcato
2022-05-25 16:45 ` Ard Biesheuvel
2022-05-25 17:01 ` Pedro Falcato
2022-05-25 22:38 ` Yao, Jiewen
2022-05-25 22:48 ` Pedro Falcato
2022-05-25 22:58 ` Yao, Jiewen
2022-05-25 23:31 ` Pedro Falcato
2022-05-25 23:35 ` Yao, Jiewen
2022-05-25 23:54 ` Pedro Falcato
2022-05-26 0:05 ` Yao, Jiewen
2022-05-26 8:29 ` 回复: " gaoliming
2022-05-25 16:57 ` Rebecca Cran
2022-05-27 5:52 ` 回复: " gaoliming
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=CAMj1kXFsQNmYbAHZ5vnp3kP_q2P98cjKSaEn+55Q7vLC2KaF1g@mail.gmail.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