unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Bremner <david@tethera.net>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>,
	Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: doc build warnings when building out-of-tree
Date: Sat, 30 May 2020 13:28:47 -0300	[thread overview]
Message-ID: <87367htmio.fsf@tethera.net> (raw)
In-Reply-To: <87wo4yhbm2.fsf@fifthhorseman.net>

Daniel Kahn Gillmor <dkg@fifthhorseman.net> writes:

> When building out-of-tree, the documentation (both manpages and info
> files) are incomplete, but they do not explicitly fail.  build logs
> follow from doing "mkdir build && ../configure && make".
>
> If there's a way to make these warnings into hard failures, i think that
> would be good -- we don't want to accidentally ship the output they
> create.  And of course actually fixing it would be even better.
>
> I'm afraid i'm not proficient enough in sphinx to know how to do either,
> so i'm just reporting a bug for now.
>

I can't duplicate these errors with sphinx-doc 2.4.3-3 on Debian.

Are the rsti files actually being built before calling sphinx-build?

d

  reply	other threads:[~2020-05-30 16:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-26 17:03 doc build warnings when building out-of-tree Daniel Kahn Gillmor
2020-05-30 16:28 ` David Bremner [this message]
2020-05-31 12:26   ` David Bremner
2020-05-31 16:15     ` [PATCH] doc: fix for out-of-tree builds of notmuch-emacs docs David Bremner
2020-05-31 20:29       ` Tomi Ollila
2020-06-01 12:12         ` David Bremner

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

  List information: https://notmuchmail.org/

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

  git send-email \
    --in-reply-to=87367htmio.fsf@tethera.net \
    --to=david@tethera.net \
    --cc=dkg@fifthhorseman.net \
    --cc=notmuch@notmuchmail.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.
Code repositories for project(s) associated with this public inbox

	https://yhetil.org/notmuch.git/

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 read-only IMAP folder(s) and NNTP newsgroup(s).