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 15:29:42 +0200 [thread overview]
Message-ID: <CALwxeUtUVAFCfXc-UPTT2cad2+v=uFdHpHooTCswFaR1=QJZzw@mail.gmail.com> (raw)
In-Reply-To: <CALwxeUvhfAWW8Jb4aZ+h5w7a0yZUEP8Qx66g4gAt6tfvZuv6HQ@mail.gmail.com>
On Mon, Sep 17, 2018 at 1:34 PM, David Marchand
<david.marchand@6wind.com> wrote:
> On Mon, Sep 17, 2018 at 12:15 PM, Thomas Monjalon <thomas@monjalon.net> wrote:
>> 17/09/2018 11:59, David Marchand:
>>> 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.
In the end, nothing special.
Just references to other docs or cross doc links.
--
David Marchand
prev parent reply other threads:[~2018-09-17 13:30 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
2018-09-17 13:29 ` David Marchand [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='CALwxeUtUVAFCfXc-UPTT2cad2+v=uFdHpHooTCswFaR1=QJZzw@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).