From: "Rebecca Cran" <rebecca@bsdio.com>
To: devel@edk2.groups.io, Anthony Perard <anthony.perard@citrix.com>,
Julien Grall <julien@xen.org>, Laszlo Ersek <lersek@redhat.com>,
Ard Biesheuvel <ard.biesheuvel@arm.com>
Subject: OvmfPkg XenPkg: X64 DEBUG GCC5 -DDEBUG_ON_SERIAL_PORT=TRUE build is broken
Date: Tue, 14 Apr 2020 12:01:14 -0600 [thread overview]
Message-ID: <e1f7e62c-adb4-eace-3828-7d73ae59ecd4@bsdio.com> (raw)
I was trying to build OvmfPkg/XenPkg -a X64 -t GCC5 -b DEBUG
-DDEBUG_ON_SERIAL_PORT=TRUE, but the build fails. Both plain DEBUG and
RELEASE builds without trying to put the debug output on the serial port
work.
[bcran@smic ~/src/tmp/edk2]$ build -p OvmfPkg/OvmfXen.dsc -a X64 -t GCC5
-b DEBUG -DDEBUG_ON_SERIAL_PORT=TRUE
Build environment: FreeBSD-13.0-CURRENT-amd64-64bit-ELF
Build start time: 11:59:24, Apr.14 2020
WORKSPACE = /home/bcran/src/tmp/edk2
EDK_TOOLS_PATH = /home/bcran/src/tmp/edk2/BaseTools
CONF_PATH = /home/bcran/src/tmp/edk2/Conf
PYTHON_COMMAND = /usr/local/bin/python3
Processing meta-data .
Architecture(s) = X64
Build target = DEBUG
Toolchain = GCC5
Active Platform = /home/bcran/src/tmp/edk2/OvmfPkg/OvmfXen.dsc
.
build.py...
/home/bcran/src/tmp/edk2/OvmfPkg/OvmfXen.dsc(...): error F002: Library
[/home/bcran/src/tmp/edk2/MdePkg/Library/UefiBootServicesTableLib/UefiBootServicesTableLib.inf]
with constructors has a cycle
consumed by
/home/bcran/src/tmp/edk2/MdePkg/Library/UefiLib/UefiLib.inf
consumed by
/home/bcran/src/tmp/edk2/MdePkg/Library/UefiDevicePathLibDevicePathProtocol/UefiDevicePathLibDevicePathProtocol.inf
- Failed -
Build end time: 11:59:25, Apr.14 2020
Build total time: 00:00:02
--
Rebecca Cran
next reply other threads:[~2020-04-14 18:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-14 18:01 Rebecca Cran [this message]
2020-04-15 14:04 ` OvmfPkg XenPkg: X64 DEBUG GCC5 -DDEBUG_ON_SERIAL_PORT=TRUE build is broken Laszlo Ersek
2020-04-15 14:20 ` Rebecca Cran
2020-04-16 16:52 ` [edk2-devel] " Laszlo Ersek
2020-04-20 12:38 ` Anthony PERARD
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=e1f7e62c-adb4-eace-3828-7d73ae59ecd4@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