On Thu, 09 Feb 2017, Jim Davis <jim.epost@xxxxxxxxx> wrote:
> On a Fedora 25 system, make pdfdocs is failing with
>
> [jim@krebstar linux-rc]$ grep -v -i 'warning:' /tmp/make-pdfdocs.err
> /data/linux-rc/Documentation/doc-guide/sphinx.rst:110: ERROR: Unknown
> target name: "sphinx c domain".
This one is caused by 1dc4bbf0b268 ("docs-rst: doc-guide: split the
kernel-documentation.rst contents"). Both kernel-doc.rst and sphinx.rst
reference Sphinx C Domain, but only kernel-doc.rst copied it over from
the source document. sphinx.rst lacks:
.. _Sphinx C Domain: http://www.sphinx-doc.org/en/stable/domains.html
Not sure if this one is able to eventually cause the pdfdocs failure.
BR,
Jani.
> ./include/net/cfg80211.h:3154: ERROR: Unexpected indentation.
> ./include/net/mac80211.h:3214: ERROR: Unexpected indentation.
> ./include/net/mac80211.h:3219: ERROR: Unexpected indentation.
> ./include/net/mac80211.h:1773: ERROR: Unexpected indentation.
> ./kernel/time/timer.c:1240: ERROR: Unexpected indentation.
> ./kernel/time/timer.c:1242: ERROR: Unexpected indentation.
> ./include/linux/wait.h:124: ERROR: Unexpected indentation.
> ./include/linux/spi/spi.h:369: ERROR: Unexpected indentation.
> ./drivers/usb/core/message.c:481: ERROR: Unexpected indentation.
> /data/linux-rc/Documentation/driver-api/usb.rst:623: ERROR: Unknown
> target name: "usb_type".
> /data/linux-rc/Documentation/driver-api/usb.rst:623: ERROR: Unknown
> target name: "usb_dir".
> /data/linux-rc/Documentation/driver-api/usb.rst:623: ERROR: Unknown
> target name: "usb_recip".
> /data/linux-rc/Documentation/driver-api/usb.rst:689: ERROR: Unknown
> target name: "usbdevfs_urb_type".
> ./sound/soc/soc-core.c:2508: ERROR: Unknown target name: "snd_soc_daifmt".
> ./sound/core/jack.c:312: ERROR: Unknown target name: "snd_jack_btn".
> make[2]: *** [linux-user.pdf] Error 1
> make[1]: *** [pdfdocs] Error 2
> make: *** [pdfdocs] Error 2
--
Jani Nikula, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
