From: "Ard Biesheuvel" <ard.biesheuvel@linaro.org>
To: Leif Lindholm <leif.lindholm@linaro.org>
Cc: edk2-devel-groups-io <devel@edk2.groups.io>,
"Gao, Liming" <liming.gao@intel.com>,
Laszlo Ersek <lersek@redhat.com>,
"Feng, Bob C" <bob.c.feng@intel.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [BUG] building multiple versions of a single platform is broken again
Date: Fri, 6 Dec 2019 14:45:36 +0000 [thread overview]
Message-ID: <CAKv+Gu8eEj=WXw_h38zz-eDka63n+MMZJOa0efB+gmcsg8-1Vw@mail.gmail.com> (raw)
In-Reply-To: <20191206144054.GS7359@bivouac.eciton.net>
On Fri, 6 Dec 2019 at 14:40, Leif Lindholm <leif.lindholm@linaro.org> wrote:
>
> On Fri, Dec 06, 2019 at 14:29:28 +0000, Ard Biesheuvel wrote:
> > When I build DEBUG and RELEASE versions of the same platform in one go, like
> >
> > build -b DEBUG -b RELEASE -a X64 -p OvmfPkg/OvmfPkgX64.dsc -t GCC5
> >
> > the first build completes, but the second one fails immediately like below.
> >
> > This appears to have gotten broken between edk2-stable201905 and
> > edk2-stable201908, but it would be nice to fix nonetheless.
>
> https://bugzilla.tianocore.org/show_bug.cgi?id=2371 ?
>
> Does the second one build if you re-run the build command?
>
Yes. So it is the exact same issue, and it is still broken.
next prev parent reply other threads:[~2019-12-06 14:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-06 14:29 [BUG] building multiple versions of a single platform is broken again Ard Biesheuvel
2019-12-06 14:40 ` Leif Lindholm
2019-12-06 14:45 ` Ard Biesheuvel [this message]
2019-12-10 8:31 ` Ard Biesheuvel
2019-12-10 13:46 ` [edk2-devel] " Bob Feng
2019-12-10 14:11 ` Ard Biesheuvel
2019-12-10 14:24 ` Bob Feng
[not found] ` <15DF08A04D983467.14068@groups.io>
2019-12-10 15:25 ` Bob Feng
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='CAKv+Gu8eEj=WXw_h38zz-eDka63n+MMZJOa0efB+gmcsg8-1Vw@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