From: David Marchand <david.marchand@6wind.com>
To: Thomas Monjalon <thomas@monjalon.net>
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 13:34:59 +0200 [thread overview]
Message-ID: <CALwxeUvhfAWW8Jb4aZ+h5w7a0yZUEP8Qx66g4gAt6tfvZuv6HQ@mail.gmail.com> (raw)
In-Reply-To: <13484845.OeNmVBkQ8T@xps>
On Mon, Sep 17, 2018 at 12:15 PM, Thomas Monjalon <thomas@monjalon.net> wrote:
> 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
I followed this doc, yes.
> Is it enough? Or is there a miss?
I am more under the impression that there is a pb.
# on a fresh Ubuntu 16.04,
root@ubuntu1604:~# apt-cache rdepends latexmk
latexmk
Reverse Depends:
latexila
texlive-full
texlive-full
texlive-extra-utils
# and on my ubuntu 18.04
marchand@gribouille:~$ apt-cache rdepends latexmk
latexmk
Reverse Depends:
latexila
texlive-full
texlive-extra-utils
python-sphinx
python3-sphinx
jupyter-sphinx-theme-doc
texlive-latex-extra does not depend on latexmk.
So 16.04 vs 18.04 is not the issue.
Looking again at 16.04 :
root@ubuntu1604:~# apt-cache depends latexila |grep latexmk
Recommends: latexmk
root@ubuntu1604:~# apt-cache depends texlive-full |grep latexmk
Depends: latexmk
root@ubuntu1604:~# apt-cache depends texlive-extra-utils |grep latexmk
Suggests: latexmk
So texlive-full is the only that has a hard dependency on it.
>> 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?
Two types of warnings, "unknown label" and "unknown document".
The "unknown label" warnings seem to be cross doc links, yes.
But some unknown document warnings are odd to me.
I will look at this a bit more.
--
David Marchand
next prev parent reply other threads:[~2018-09-17 11:35 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
2018-09-17 11:34 ` David Marchand [this message]
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=CALwxeUvhfAWW8Jb4aZ+h5w7a0yZUEP8Qx66g4gAt6tfvZuv6HQ@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).