From: Stefan Hajnoczi <stefanha@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Kevin Wolf <kwolf@redhat.com>, Fam Zheng <fam@euphon.net>,
Eduardo Habkost <ehabkost@redhat.com>,
Qemu-block <qemu-block@nongnu.org>,
QEMU Developers <qemu-devel@nongnu.org>,
Max Reitz <mreitz@redhat.com>, Cleber Rosa <crosa@redhat.com>
Subject: Re: [PULL 00/17] Block patches
Date: Mon, 5 Oct 2020 14:26:06 +0100 [thread overview]
Message-ID: <20201005132606.GA5029@stefanha-x1.localdomain> (raw)
In-Reply-To: <CAFEAcA9JdhSSJesCLB=F+GMc-wK4+ukHQwA18wdU7HaqoPiTfg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2220 bytes --]
On Thu, Oct 01, 2020 at 04:12:12PM +0100, Peter Maydell wrote:
> On Thu, 1 Oct 2020 at 16:03, Stefan Hajnoczi <stefanha@redhat.com> wrote:
> >
> > On Thu, Oct 01, 2020 at 12:23:00PM +0100, Peter Maydell wrote:
> > > This produces this error message on ppc64be Linux:
> > >
> > > make: Entering directory `/home/pm215/qemu/build/all'
> > > make[1]: Entering directory `/home/pm215/qemu/slirp'
> > > make[1]: Nothing to be done for `all'.
> > > make[1]: Leaving directory `/home/pm215/qemu/slirp'
> > > Generating qemu-version.h with a meson_exe.py custom command
> > > Generating qemu-options.def with a meson_exe.py custom command
> > > Generating block-gen.c with a custom command
> > > YAML:1:83: error: unknown enumerated scalar
> > > {"IndentWidth": 4, "BraceWrapping": {"AfterFunction": true},
> > > "BreakBeforeBraces": "Custom", "SortIncludes": false,
> > > "MaxEmptyLinesToKeep": 2}
> > >
> > > ^~~~~~~~
> > > Error parsing -style: Invalid argument, using LLVM style
> > > YAML:1:83: error: unknown enumerated scalar
> > > {"IndentWidth": 4, "BraceWrapping": {"AfterFunction": true},
> > > "BreakBeforeBraces": "Custom", "SortIncludes": false,
> > > "MaxEmptyLinesToKeep": 2}
> > >
> > > ^~~~~~~~
> > > Error parsing -style: Invalid argument, using LLVM style
> > > Compiling C object libqemuutil.a.p/util_qemu-error.c.o
> > > Compiling C object libqemuutil.a.p/util_qemu-sockets.c.o
> > > Compiling C object libqemuutil.a.p/util_aio-posix.c.o
> > > Compiling C object libqemuutil.a.p/util_osdep.c.o
> > >
> > > The error does not cause the build to fail, which seems
> > > like it's also a bug...
> > >
> > > (My guess is this is due to some script implicitly wanting
> > > a newer version of something or other than the PPC box
> > > happens to have installed, rather than being an endianness
> > > issue.)
> >
> > Please rerun with make -j1 V=1 so the full command is printed. I'm not
> > sure what is emitting these errors.
>
> Build tree already overwritten to handle a different pullreq,
> I'm afraid. I can come back and retry later...
No problem. Thanks for pointing out the issue, Vladimir and Peter.
I will send a v2.
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-10-05 13:28 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-30 10:12 [PULL 00/17] Block patches Stefan Hajnoczi
2020-09-30 10:12 ` [PULL 01/17] util/vfio-helpers: Pass page protections to qemu_vfio_pci_map_bar() Stefan Hajnoczi
2020-09-30 10:12 ` [PULL 02/17] block/nvme: Map doorbells pages write-only Stefan Hajnoczi
2020-09-30 10:12 ` [PULL 03/17] block/nvme: Reduce I/O registers scope Stefan Hajnoczi
2020-09-30 10:12 ` [PULL 04/17] block/nvme: Drop NVMeRegs structure, directly use NvmeBar Stefan Hajnoczi
2020-09-30 10:12 ` [PULL 05/17] block/nvme: Use register definitions from 'block/nvme.h' Stefan Hajnoczi
2020-09-30 10:12 ` [PULL 06/17] block/nvme: Replace magic value by SCALE_MS definition Stefan Hajnoczi
2020-09-30 10:12 ` [PULL 07/17] block: return error-code from bdrv_invalidate_cache Stefan Hajnoczi
2020-09-30 10:12 ` [PULL 08/17] block/io: refactor coroutine wrappers Stefan Hajnoczi
2020-09-30 10:12 ` [PULL 09/17] block: declare some coroutine functions in block/coroutines.h Stefan Hajnoczi
2020-09-30 10:12 ` [PULL 10/17] scripts: add block-coroutine-wrapper.py Stefan Hajnoczi
2020-09-30 10:12 ` [PULL 11/17] block: generate coroutine-wrapper code Stefan Hajnoczi
2020-09-30 10:13 ` [PULL 12/17] block: drop bdrv_prwv Stefan Hajnoczi
2020-09-30 10:13 ` [PULL 13/17] block/io: refactor save/load vmstate Stefan Hajnoczi
2020-09-30 10:13 ` [PULL 14/17] include/block/block.h: drop non-ascii quotation mark Stefan Hajnoczi
2020-09-30 10:13 ` [PULL 15/17] docs: add 'io_uring' option to 'aio' param in qemu-options.hx Stefan Hajnoczi
2020-09-30 10:13 ` [PULL 16/17] util/vfio-helpers: Collect IOVA reserved regions Stefan Hajnoczi
2020-09-30 10:13 ` [PULL 17/17] util/vfio-helpers: Rework the IOVA allocator to avoid " Stefan Hajnoczi
2020-10-01 11:23 ` [PULL 00/17] Block patches Peter Maydell
2020-10-01 13:56 ` Vladimir Sementsov-Ogievskiy
2020-10-01 15:02 ` Stefan Hajnoczi
2020-10-01 15:12 ` Peter Maydell
2020-10-05 13:26 ` Stefan Hajnoczi [this message]
2020-10-01 15:29 ` Vladimir Sementsov-Ogievskiy
2020-10-02 10:36 ` Peter Maydell
-- strict thread matches above, loose matches on Subject: below --
2023-06-05 15:45 Hanna Czenczek
2023-06-05 19:03 ` Richard Henderson
2023-04-28 12:39 Stefan Hajnoczi
2023-04-29 22:05 ` Richard Henderson
2023-05-01 11:56 ` Stefan Hajnoczi
2020-02-06 12:51 Max Reitz
2020-02-06 18:58 ` Peter Maydell
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-all 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=20201005132606.GA5029@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=crosa@redhat.com \
--cc=ehabkost@redhat.com \
--cc=fam@euphon.net \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).