From: "Tobin C. Harding" <me@tobin.cc>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org
Subject: undefined label
Date: Thu, 7 Mar 2019 20:17:34 +1100 [thread overview]
Message-ID: <20190307091734.GB9152@eros.localdomain> (raw)
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)
This is a hell of a gotcha, I wasted a bunch of cycles baffled as to why
that label was not defined today :( Super excited that I worked out why
while day dreaming though.
Last time I sent in the 'fix' I must built with SPHINXDIRS, patched then
built without SPHINXDIRS and thought the patch fixed it.
Anyways, hope you get a chuckle out of this.
All the best,
Tobin.
next reply other threads:[~2019-03-07 9:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-07 9:17 Tobin C. Harding [this message]
2019-03-07 9:58 ` undefined label Markus Heiser
2019-03-07 20:30 ` Tobin C. Harding
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:
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=20190307091734.GB9152@eros.localdomain \
--to=me@tobin.cc \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
/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