All of
 help / color / mirror / Atom feed
From: "Tobin C. Harding" <>
To: Markus Heiser <>
Cc: Jonathan Corbet <>,
Subject: Re: undefined label
Date: Fri, 8 Mar 2019 07:30:41 +1100	[thread overview]
Message-ID: <20190307203041.GC21937@eros.localdomain> (raw)
In-Reply-To: <>

On Thu, Mar 07, 2019 at 10:58:07AM +0100, Markus Heiser wrote:
> Am 07.03.19 um 10:17 schrieb Tobin C. Harding:
> > Hi Jon,
> > 
> > I hit that undefined label warning again today.  Then just now I was
> > sitting enjoying a quite scotch and the reason came to me.  It is caused
> > by building part of the docs instead of the whole tree i.e. using
> > 
> > 	make SPHINXDIRS=admin-guide htmldocs
> > 
> > Gives the warning
> > 
> > 	WARNING: undefined label: numa (if the link has no caption the label must precede a section header)
> The label 'numa' is not a part of the admin-guide (book), it is set in
> the vm (book): Documentation/vm/numa.rst:1
> If compiling only a book like admin-guide, those links are broken.  Its not only
> 'numa' which is broken and its not only the admin-guide which has cross-books
> links in.
> To close such cross-books links we can use intersphinx [1] and map to e.g.
>   intersphinx_mapping = {
>       'kernel': ('', None)}
> If there is any interest in, I can implement a RFC for this.

Cool!  I think this would be super useful, I for one like using
SPHINXDIRS when developing docs incrementally so removing false warnings
would be nice.  I doubt I'm the only one to be baffled about Sphinx
references.  I'd be happy to review and test your RFC if you CC me.


  reply	other threads:[~2019-03-07 20:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-07  9:17 undefined label Tobin C. Harding
2019-03-07  9:58 ` Markus Heiser
2019-03-07 20:30   ` Tobin C. Harding [this message]
2019-03-08  8:56     ` Markus Heiser
2019-03-08 12:17       ` Jani Nikula
2019-03-11 17:30         ` Jonathan Corbet
2019-03-12  7:57           ` Jani Nikula
2019-03-12  8:19           ` Markus Heiser

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190307203041.GC21937@eros.localdomain \ \ \ \ \

* 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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.