From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Stephen Hemminger" <stephen@networkplumber.org>,
"Burakov, Anatoly" <anatoly.burakov@intel.com>
Cc: "Ferruh Yigit" <ferruh.yigit@intel.com>,
"Thomas Monjalon" <thomas@monjalon.net>,
"John McNamara" <john.mcnamara@intel.com>,
"Marko Kovacevic" <marko.kovacevic@intel.com>, <dev@dpdk.org>
Subject: Re: [dpdk-dev] make doc fails
Date: Mon, 24 Jun 2019 18:09:59 +0200 [thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35B4297E@smartserver.smartshare.dk> (raw)
In-Reply-To: <20190624082739.24eccb33@hermes.lan>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Stephen Hemminger
> Sent: Monday, June 24, 2019 5:28 PM
>
> On Mon, 24 Jun 2019 16:04:15 +0100
> "Burakov, Anatoly" <anatoly.burakov@intel.com> wrote:
>
> > On 24-Jun-19 3:53 PM, Ferruh Yigit wrote:
> > > On 6/23/2019 11:46 PM, Thomas Monjalon wrote:
> > >> 21/06/2019 21:56, Stephen Hemminger:
> > >>> Just tried make doc on current DPDK tree and it fails:
> > >>>
> > >>> /home/shemminger/git/dpdk/doc/guides/faq/faq.rst:7: WARNING:
> undefined label: linux_gsg (if the link has no caption the label must
> precede a section header)
> > >>> /home/shemminger/git/dpdk/doc/guides/faq/faq.rst:25: WARNING:
> undefined label: linux_gsg (if the link has no caption the label must
> precede a section header)
> > >>> /home/shemminger/git/dpdk/doc/guides/faq/faq.rst:190: WARNING:
> undefined label: multi_process_app (if the link has no caption the label
> must precede a section header)
> > >>
> > >>
> > >> These are only warnings, not fatal failues.
> > >>
> > >>> Not sure what the bad commit is. Also, not sure why CI didn't catch
> it.
> > >>
> > >> It works well on my machine (with some warnings).
> > >
> > >
> > > The warnings are from .pdf conversion and they are there for a long
> time now,
> > > although there are warnings pdf files still generated.
> > >
> > > html files are generated by 'make doc-guides-html' and completes
> without
> > > warning, which verifies the .rst file syntax.
> > >
> >
> > PDF's can't link to other PDF's (e.g. FAQ can't link to GSG), that's why
> > these warnings happen. That's normal.
> >
>
> Ok thanks for the explanation
Shouldn't the Makefile print a message to expect this warning just before the warning is emitted, so future confusion about this is avoided?
Med venlig hilsen / kind regards
- Morten Brørup
prev parent reply other threads:[~2019-06-24 16:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 19:56 Stephen Hemminger
2019-06-23 22:46 ` Thomas Monjalon
2019-06-24 14:53 ` Ferruh Yigit
2019-06-24 15:04 ` Burakov, Anatoly
2019-06-24 15:27 ` Stephen Hemminger
2019-06-24 16:09 ` Morten Brørup [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=98CBD80474FA8B44BF855DF32C47DC35B4297E@smartserver.smartshare.dk \
--to=mb@smartsharesystems.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
/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).