All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: Nathan Chancellor <natechancellor@gmail.com>,
	Masahiro Yamada <masahiroy@kernel.org>,
	Michal Marek <michal.lkml@markovi.net>,
	clang-built-linux <clang-built-linux@googlegroups.com>,
	Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
	Linux Doc Mailing List <linux-doc@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Miguel Ojeda <ojeda@kernel.org>
Subject: Re: [PATCH] Documentation/llvm: Add a section about supported architectures
Date: Thu, 14 Jan 2021 07:36:15 -0700	[thread overview]
Message-ID: <20210114073615.6b9add58@lwn.net> (raw)
In-Reply-To: <CAKwvOdnJ0VUjTX-cyLgtHvy68DHG1VMj7s0huk_FKh1E9pH9Cg@mail.gmail.com>

On Wed, 13 Jan 2021 17:19:59 -0800
Nick Desaulniers <ndesaulniers@google.com> wrote:

> Patch looks fine, but `make -j htmldocs` seems to be taking forever
> for me so I can't render it. Is this a known issue?
> 
> $ make -j htmldocs
>   SPHINX  htmldocs --> file:///android0/linux-next/Documentation/output
> make[2]: Nothing to be done for 'html'.
> WARNING: The kernel documentation build process
>         support for Sphinx v3.0 and above is brand new. Be prepared for
>         possible issues in the generated output.

Sphinx 3.x is *way* slower to build the docs, alas.  One of many
"improvements" we got with that change.

jon

  parent reply	other threads:[~2021-01-14 14:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-14  0:34 [PATCH] Documentation/llvm: Add a section about supported architectures Nathan Chancellor
2021-01-14  1:19 ` Nick Desaulniers
2021-01-14  2:05   ` Nick Desaulniers
2021-01-14  2:23     ` Nathan Chancellor
2021-01-14  9:13       ` Miguel Ojeda
2021-01-14 14:36   ` Jonathan Corbet [this message]
2021-01-14 17:53     ` Nick Desaulniers
2021-01-14  7:39 ` Sedat Dilek
2021-01-29 20:31 ` Nathan Chancellor
2021-01-29 21:07   ` Masahiro Yamada

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=20210114073615.6b9add58@lwn.net \
    --to=corbet@lwn.net \
    --cc=clang-built-linux@googlegroups.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=michal.lkml@markovi.net \
    --cc=natechancellor@gmail.com \
    --cc=ndesaulniers@google.com \
    --cc=ojeda@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 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.