From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io, rebecca@bsdio.com,
Anthony Perard <anthony.perard@citrix.com>,
Julien Grall <julien@xen.org>,
Ard Biesheuvel <ard.biesheuvel@arm.com>
Subject: Re: [edk2-devel] OvmfPkg XenPkg: X64 DEBUG GCC5 -DDEBUG_ON_SERIAL_PORT=TRUE build is broken
Date: Thu, 16 Apr 2020 18:52:41 +0200 [thread overview]
Message-ID: <e4ee4b48-f2c8-5f6c-cc6c-8ef729bbea7d@redhat.com> (raw)
In-Reply-To: <d2855022-b938-1ded-fdf5-143ad3ca62c1@bsdio.com>
On 04/15/20 16:20, Rebecca Cran wrote:
> On 4/15/2020 8:04 AM, Laszlo Ersek wrote:
>>
>> I figure you attempted the DEBUG_ON_SERIAL_PORT build because without it
>> you get no debug output at all (due to the default
>> PlatformDebugLibIoPort resolution, which produces no logs on Xen).
>
> I just attempted the DEBUG_ON_SERIAL_PORT build because that's how I do
> the other DEBUG OVMF builds and was running the following basic build
> script to make sure my bhyve changes weren't breaking things.
>
>
> build -p OvmfPkg/OvmfPkgX64.dsc -a X64 -t GCC5 -b RELEASE
> build -p OvmfPkg/OvmfPkgX64.dsc -a X64 -t GCC5 -b DEBUG
> -DDEBUG_ON_SERIAL_PORT=TRUE
> build -p OvmfPkg/OvmfPkgX64.dsc -a X64 -t GCC5 -b NOOPT
> build -p OvmfPkg/OvmfPkgIa32.dsc -a IA32 -t GCC5 -b RELEASE
> build -p OvmfPkg/OvmfPkgIa32.dsc -a IA32 -t GCC5 -b DEBUG
> -DDEBUG_ON_SERIAL_PORT=TRUE
> build -p OvmfPkg/OvmfPkgIa32.dsc -a IA32 -t GCC5 -b NOOPT
> build -p OvmfPkg/OvmfPkgIa32X64.dsc -a IA32 -a X64 -t GCC5 -b RELEASE
> build -p OvmfPkg/OvmfPkgIa32X64.dsc -a IA32 -a X64 -t GCC5 -b DEBUG
> -DDEBUG_ON_SERIAL_PORT=TRUE
> build -p OvmfPkg/OvmfPkgIa32X64.dsc -a IA32 -a X64 -t GCC5 -b NOOPT
> build -p OvmfPkg/OvmfXen.dsc -a X64 -t GCC5 -b RELEASE
> build -p OvmfPkg/OvmfXen.dsc -a X64 -t GCC5 -b DEBUG
> -DDEBUG_ON_SERIAL_PORT=TRUE
> build -p OvmfPkg/OvmfXen.dsc -a X64 -t GCC5 -b NOOPT
> build -p BhyvePkg/BhyvePkgX64.dsc -a X64 -t GCC5 -b RELEASE
> build -p BhyvePkg/BhyvePkgX64.dsc -a X64 -t GCC5 -b DEBUG
> -DDEBUG_ON_SERIAL_PORT=TRUE
> build -p BhyvePkg/BhyvePkgX64.dsc -a X64 -t GCC5 -b NOOPT
>
Thanks.
Then the suggestion to remove DEBUG_ON_SERIAL_PORT from OvmfXen (maybe
as a first step only?) would fit your use case too, I think.
Laszlo
next prev parent reply other threads:[~2020-04-16 16:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-14 18:01 OvmfPkg XenPkg: X64 DEBUG GCC5 -DDEBUG_ON_SERIAL_PORT=TRUE build is broken Rebecca Cran
2020-04-15 14:04 ` Laszlo Ersek
2020-04-15 14:20 ` Rebecca Cran
2020-04-16 16:52 ` Laszlo Ersek [this message]
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=e4ee4b48-f2c8-5f6c-cc6c-8ef729bbea7d@redhat.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