From: David Marchand <david.marchand@6wind.com>
To: "Mcnamara, John" <john.mcnamara@intel.com>, marko.kovacevic@intel.com
Cc: dev@dpdk.org, Thomas Monjalon <thomas@monjalon.net>,
Christian Ehrhardt <christian.ehrhardt@canonical.com>
Subject: [dpdk-dev] Warnings when building the doc on Ubuntu 18.04
Date: Mon, 17 Sep 2018 11:59:33 +0200 [thread overview]
Message-ID: <CALwxeUtqtznYy9MszrF0ovFhz1G1db0OB=SWKqEZx+sEqBWnfg@mail.gmail.com> (raw)
Hello,
I tried to build the documentation but it looks like the instructions
about how to build it are not up to date. Currently running Ubuntu
18.04, it might be the reason.
marchand@gribouille:~/git/dpdk$ make doc
[...]
lookup cache used 16122/65536 hits=132815 misses=16618
finished...
sphinx processing guides-html...
sphinx processing guides-pdf-faq...
/home/marchand/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/marchand/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/marchand/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)
pdflatex processing guides-pdf-faq...
make[2]: latexmk: Command not found
Makefile:33: recipe for target 'doc.pdf' failed
make[2]: *** [doc.pdf] Error 127
/home/marchand/git/dpdk/mk/rte.sdkdoc.mk:81: recipe for target
'guides-pdf-faq' failed
make[1]: *** [guides-pdf-faq] Error 2
/home/marchand/git/dpdk/mk/rte.sdkroot.mk:88: recipe for target 'doc-all' failed
make: *** [doc-all] Error 2
So I installed the latexmk package.
Nothing in the dpdk refers to it, so it might be an external issue.
After this, I still see those warnings (and actually a lot of others).
The pdf generated docs have no link in them, but the html ones are fine.
Is is expected ?
--
David Marchand
next reply other threads:[~2018-09-17 9:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-17 9:59 David Marchand [this message]
2018-09-17 10:15 ` Thomas Monjalon
2018-09-17 11:34 ` David Marchand
2018-09-17 13:29 ` David Marchand
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='CALwxeUtqtznYy9MszrF0ovFhz1G1db0OB=SWKqEZx+sEqBWnfg@mail.gmail.com' \
--to=david.marchand@6wind.com \
--cc=christian.ehrhardt@canonical.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.com \
--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).