From: Daniel Henrique Barboza <danielhb413@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
qemu-ppc <qemu-ppc@nongnu.org>, Greg Kurz <groug@kaod.org>,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [PATCH 1/1] docs: adding NUMA documentation for pseries
Date: Mon, 3 Aug 2020 10:30:06 -0300 [thread overview]
Message-ID: <057db3b9-1a3e-ed80-a5d6-72c82eb5c333@gmail.com> (raw)
In-Reply-To: <CAFEAcA9hV4+kKO1gggzNjNjMHxt3WiDac2KivjZzLAGExdN7Kw@mail.gmail.com>
On 8/3/20 9:59 AM, Peter Maydell wrote:
> On Mon, 3 Aug 2020 at 13:15, Daniel Henrique Barboza
> <danielhb413@gmail.com> wrote:
>> On 8/3/20 8:49 AM, Greg Kurz wrote:
>>> I'm now hitting this:
>>>
>>> Warning, treated as error:
>>> docs/specs/ppc-spapr-numa.rst:document isn't included in any toctree
>>
>> How are you hitting this? I can't reproduce this error. Tried running
>> ./autogen.sh and 'make' and didn't see it.
>
> We don't have an autogen.sh...
I intended to say ../configure and by force of habit I mentioned the Libvirt
one :(
>
> Anyway, 'make' will build the documentation, but only if you have
> the necessary tools installed. If you pass '--enable-docs' to configure
> then it will error out if you're missing something rather than
> its default of quietly not building the docs.
Thanks for the info. I used --enable-docs and discovered that I was missing
one of the doc packages. I'm seeing the error now.
Thanks,
DHB
>
> thanks
> -- PMM
>
prev parent reply other threads:[~2020-08-03 13:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 12:57 [PATCH 1/1] docs: adding NUMA documentation for pseries Daniel Henrique Barboza
2020-07-30 0:58 ` David Gibson
2020-08-03 11:49 ` Greg Kurz
2020-08-03 12:14 ` Daniel Henrique Barboza
2020-08-03 12:53 ` Greg Kurz
2020-08-03 13:43 ` Daniel Henrique Barboza
2020-08-03 12:59 ` Peter Maydell
2020-08-03 13:30 ` Daniel Henrique Barboza [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-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=057db3b9-1a3e-ed80-a5d6-72c82eb5c333@gmail.com \
--to=danielhb413@gmail.com \
--cc=david@gibson.dropbear.id.au \
--cc=groug@kaod.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).