From: Eric Blake <eblake@redhat.com>
To: Rahul Gusai <rgusai97@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] POD document had syntax errors at /usr/bin/pod2man line 68.
Date: Fri, 27 Apr 2018 08:52:53 -0500 [thread overview]
Message-ID: <9b4880b5-d082-b791-b520-532d13beaf05@redhat.com> (raw)
In-Reply-To: <CAOCZyUWKV6fko1gmdNvJdBO4pDLAjNVgVdBpYJkBfPUA42Fv7w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1137 bytes --]
On 04/27/2018 03:47 AM, Rahul Gusai wrote:
> I am getting the following error while trying to compile the binaries for
> QEMU emulator.
>
Your mailer corrupted line spacing, making it difficult to read.
> *GEN qemu.1qemu.pod around line 95: Non-ASCII character seen before
> =encoding in 'Sch�tz.'. Assuming UTF-8POD document had syntax errors at
> /usr/bin/pod2man line 68.Makefile:297: recipe for target 'qemu.1'
> failedmake: *** [qemu.1] Error 255make: *** Deleting file 'qemu.1'*
qemu.pod is a generated file; the version in my build tree starts out:
=encoding UTF-8
and then uses proper UTF-8 encoding of line 95:
by Tibor "TS" Schütz.
> What could be the issue ?
What do the following output in your setup:
$ locale
$ grep =encoding qemu.pod
$ sed -n '92,98p' qemu.pod | od -tx1z
I'm wondering if somehow you have a non-UTF-8 locale such that the
generated .pod file is encoded in a different locale, to the point that
pod2man then chokes on the file.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 619 bytes --]
next prev parent reply other threads:[~2018-04-27 13:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-27 8:47 [Qemu-devel] POD document had syntax errors at /usr/bin/pod2man line 68 Rahul Gusai
2018-04-27 13:52 ` Eric Blake [this message]
2018-04-27 13:57 ` Daniel P. Berrangé
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=9b4880b5-d082-b791-b520-532d13beaf05@redhat.com \
--to=eblake@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rgusai97@gmail.com \
/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).