From: "wanglimin" <wanglimin@xfusion.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: [edk2-devel] RELEASE build error with QEMU_PV_VARS
Date: Tue, 20 May 2025 02:09:45 +0000 [thread overview]
Message-ID: <03dce3338e0b44b2a6faeb045a86aeb8@xfusion.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 914 bytes --]
Hello,
I met undefined reference to `MmioWrite32' error when building AARCH64 with -D QEMU_PV_VARS=TRUE on RELEASE mode,
build -n 128 -p ArmVirtPkg/ArmVirtQemu.dsc -a AARCH64 -b RELEASE -D QEMU_PV_VARS=TRUE -t GCC5
…
OvmfPkg/VirtMmCommunicationDxe/QemuMmio.c:159: undefined reference to `MmioWrite32'
OvmfPkg/VirtMmCommunicationDxe/QemuMmio.c:161: undefined reference to `MmioRead32'
….
It is built successfully without the option QEMU_PV_VARS, or build with DEBUG mode.
Not sure if I am missing anything?
Best Regards
Limin Wang.
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#121351): https://edk2.groups.io/g/devel/message/121351
Mute This Topic: https://groups.io/mt/113204735/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: 5693 bytes --]
next reply other threads:[~2025-05-20 2:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-20 2:09 wanglimin [this message]
2025-05-20 2:24 ` [edk2-devel] RELEASE build error with QEMU_PV_VARS wanglimin
2025-05-20 6:37 ` Gerd Hoffmann via groups.io
2025-05-20 7:00 ` wanglimin
[not found] ` <18412A1684644090.26643@groups.io>
2025-05-20 9:23 ` wanglimin
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=03dce3338e0b44b2a6faeb045a86aeb8@xfusion.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