From: Peter Maydell <peter.maydell@linaro.org>
To: Markus Armbruster <armbru@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PULL 00/12] QAPI patches for 2019-10-22
Date: Tue, 22 Oct 2019 10:32:50 +0100 [thread overview]
Message-ID: <CAFEAcA-zmrcD-6pLTMuFLYCkGrJdA8bZjkBOHwoF0fWqGzKdMg@mail.gmail.com> (raw)
In-Reply-To: <20191022075615.956-1-armbru@redhat.com>
On Tue, 22 Oct 2019 at 09:11, Markus Armbruster <armbru@redhat.com> wrote:
>
> The following changes since commit e9d42461920f6f40f4d847a5ba18e90d095ed0b9:
>
> Merge remote-tracking branch 'remotes/kraxel/tags/audio-20191018-pull-request' into staging (2019-10-18 14:13:11 +0100)
>
> are available in the Git repository at:
>
> git://repo.or.cz/qemu/armbru.git tags/pull-qapi-2019-10-22
>
> for you to fetch changes up to 0582bce69e8688fd7dd5501d352695e5c675b89b:
>
> qapi: Allow introspecting fix for savevm's cooperation with blockdev (2019-10-22 09:28:11 +0200)
>
> ----------------------------------------------------------------
> QAPI patches for 2019-10-22
>
> ----------------------------------------------------------------
Fails to build:
GEN qapi-gen
make[1]: Nothing to be done for `all'.
Traceback (most recent call last):
File "/Users/pm215/src/qemu-for-merges/scripts/qapi-gen.py", line
13, in <module>
from qapi.commands import gen_commands
File "/Users/pm215/src/qemu-for-merges/scripts/qapi/commands.py",
line 17, in <module>
from qapi.gen import QAPIGenCCode, QAPISchemaModularCVisitor, ifcontext
File "/Users/pm215/src/qemu-for-merges/scripts/qapi/gen.py", line 8
SyntaxError: Non-ASCII character '\xc3' in file
/Users/pm215/src/qemu-for-merges/scripts/qapi/gen.py on line 8, but no
encoding declared; see http://python.org/dev/peps/pep-0263/ for
details
make: *** [qapi-gen-timestamp] Error 1
thanks
-- PMM
next prev parent reply other threads:[~2019-10-22 9:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-22 7:56 [PULL 00/12] QAPI patches for 2019-10-22 Markus Armbruster
2019-10-22 7:56 ` [PULL 01/12] qapi: Don't suppress doc generation without pragma doc-required Markus Armbruster
2019-10-22 7:56 ` [PULL 02/12] qapi: Store pragma state in QAPISourceInfo, not global state Markus Armbruster
2019-10-22 7:56 ` [PULL 03/12] qapi: Eliminate accidental global frontend state Markus Armbruster
2019-10-22 7:56 ` [PULL 04/12] qapi: Speed up frontend tests Markus Armbruster
2019-10-22 7:56 ` [PULL 05/12] qapi: Move gen_enum(), gen_enum_lookup() back to qapi/types.py Markus Armbruster
2019-10-22 7:56 ` [PULL 06/12] qapi: Split up scripts/qapi/common.py Markus Armbruster
2019-10-22 7:56 ` [PULL 07/12] qapi: Clear scripts/qapi/doc.py executable bits again Markus Armbruster
2019-10-22 7:56 ` [PULL 08/12] tests/qapi-schema: Tidy up test output indentation Markus Armbruster
2019-10-22 7:56 ` [PULL 09/12] qapi: Add feature flags to commands Markus Armbruster
2019-10-22 7:56 ` [PULL 10/12] tests: qapi: Test 'features' of commands Markus Armbruster
2019-10-22 7:56 ` [PULL 11/12] tests/qapi-schema: Cover feature documentation comments Markus Armbruster
2019-10-22 7:56 ` [PULL 12/12] qapi: Allow introspecting fix for savevm's cooperation with blockdev Markus Armbruster
2019-10-22 9:32 ` Peter Maydell [this message]
2019-10-22 10:49 ` [PULL 00/12] QAPI patches for 2019-10-22 Markus Armbruster
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=CAFEAcA-zmrcD-6pLTMuFLYCkGrJdA8bZjkBOHwoF0fWqGzKdMg@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=armbru@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.