From: Thomas Monjalon <thomas@monjalon.net>
To: David Marchand <david.marchand@6wind.com>
Cc: "Mcnamara, John" <john.mcnamara@intel.com>,
marko.kovacevic@intel.com, dev@dpdk.org,
Christian Ehrhardt <christian.ehrhardt@canonical.com>
Subject: Re: [dpdk-dev] Warnings when building the doc on Ubuntu 18.04
Date: Mon, 17 Sep 2018 12:15:08 +0200 [thread overview]
Message-ID: <13484845.OeNmVBkQ8T@xps> (raw)
In-Reply-To: <CALwxeUtqtznYy9MszrF0ovFhz1G1db0OB=SWKqEZx+sEqBWnfg@mail.gmail.com>
17/09/2018 11:59, David Marchand:
> 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.
In pkg/dpdk.spec, there is this requirement (for RedHat based distro):
doxygen, python-sphinx, inkscape, texlive-collection-latexextra
I am not sure it is up to date though.
There is also a guide listing the dependencies:
doc/guides/contributing/documentation.rst
Here, it is mentioned
TexLive (at least TexLive-core and the extra Latex support)
and
# Ubuntu/Debian.
sudo apt-get -y install texlive-latex-extra
Is it enough? Or is there a miss?
[...]
> So I installed the latexmk package.
> Nothing in the dpdk refers to it, so it might be an external issue.
Is latexmk a dependency of texlive-latex-extra?
> 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 ?
The warnings are about the cross-doc links.
I think links are working inside a PDF but obviously not when referencing
another PDF document.
Do you see a different issue?
next prev parent reply other threads:[~2018-09-17 10:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-17 9:59 David Marchand
2018-09-17 10:15 ` Thomas Monjalon [this message]
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=13484845.OeNmVBkQ8T@xps \
--to=thomas@monjalon.net \
--cc=christian.ehrhardt@canonical.com \
--cc=david.marchand@6wind.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.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).