From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: Marcin Wojtas <mw@semihalf.com>
Cc: Laszlo Ersek <lersek@redhat.com>,
"Gao, Liming" <liming.gao@intel.com>,
Leif Lindholm <leif.lindholm@linaro.org>,
"Feng, Bob C" <bob.c.feng@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [Patch V2] BaseTool: Fixed incremental rebuild issue.
Date: Sat, 23 Feb 2019 11:48:18 +0100 [thread overview]
Message-ID: <CAKv+Gu_oq2xcDgnSeW5+V8HWqVr+PRA+T9fq38OL-PzVH6fj8g@mail.gmail.com> (raw)
In-Reply-To: <CAPv3WKfo2bot8N+LUaf9F+PYXo9JRP+DYOUmTfD=2oqnpDEfbA@mail.gmail.com>
On Sat, 23 Feb 2019 at 11:14, Marcin Wojtas <mw@semihalf.com> wrote:
>
> Hi Laszlo,
>
> pt., 22 lut 2019 o 21:08 Laszlo Ersek <lersek@redhat.com> napisał(a):
> >
> > On 02/22/19 20:21, Ard Biesheuvel wrote:
> > > On Fri, 22 Feb 2019 at 08:26, Gao, Liming <liming.gao@intel.com> wrote:
> > >>
> > >> Reviewed-by: Liming Gao <liming.gao@intel.com>
> > >>
> > >
> > > Incremental builds are still broken for me, even with this patch. Is
> > > anyone else seeing the same?
> >
> > I am not; but I've been using Python3.4 for a while now (it is needed by
> > another package on my system, and then the build tools find it too).
> >
> > The regression is attributed to commit d943b0c339fe ("BaseTools: Handle
> > the bytes and str difference", 2019-02-01), which I believe is related
> > to the python2/3 conversion. So I assume python3.4 masks the problem.
> >
>
> In my setup with the latest BaseTools update this problem is gone. I'm
> using Python 3.5.2.
>
Thanks for confirming.
I did a full clean of my workspace, and now things are working for me
again as well.
Thanks,
prev parent reply other threads:[~2019-02-23 10:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-20 15:21 [Patch V2] BaseTool: Fixed incremental rebuild issue Feng, Bob C
2019-02-22 7:26 ` Gao, Liming
2019-02-22 19:21 ` Ard Biesheuvel
2019-02-22 20:08 ` Laszlo Ersek
2019-02-23 10:14 ` Marcin Wojtas
2019-02-23 10:48 ` Ard Biesheuvel [this message]
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+Gu_oq2xcDgnSeW5+V8HWqVr+PRA+T9fq38OL-PzVH6fj8g@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