From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 364] Do not generate temporary doc files in the sources
Date: Tue, 12 Nov 2019 14:13:56 +0000 [thread overview]
Message-ID: <bug-364-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=364
Bug ID: 364
Summary: Do not generate temporary doc files in the sources
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: enhancement
Priority: Normal
Component: doc
Assignee: dev@dpdk.org
Reporter: david.marchand@redhat.com
Target Milestone: ---
At the moment, when building the documentation, some temporary files are
created in the sources directories.
When switching branches and compiling the documentation for older releases (for
example building a 17.11 documentation, with a master documentation built
before) , this can trigger hard to understand build errors like:
Sphinx error:
master file .../doc/guides/compressdevs/index.rst not found
make[1]: *** [.../mk/rte.sdkdoc.mk:110: guides-pdf-compressdevs] Error 2
make: *** [.../mk/rte.sdkroot.mk:116: doc-all] Error 2
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2019-11-12 14:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-364-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@dpdk.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).