From: Jonathan Corbet <corbet@lwn.net>
To: Bhaskar Chowdhury <unixbhaskar@gmail.com>
Cc: LinuxKernel <linux-kernel@vger.kernel.org>
Subject: Re: Kernel build failed ...SPHINX extension error
Date: Wed, 8 Apr 2020 13:25:05 -0600 [thread overview]
Message-ID: <20200408132505.52e595bc@lwn.net> (raw)
In-Reply-To: <20200408113705.GB1924@ArchLinux>
On Wed, 8 Apr 2020 17:07:05 +0530
Bhaskar Chowdhury <unixbhaskar@gmail.com> wrote:
> Extension error:
> Could not import extension cdomain (exception: cannot import name
> 'c_funcptr_sig_re' from 'sphinx.domains.c'
> (/usr/lib/python3.8/site-packages/sphinx/domains/c.py))
> Apr 08 16:48:46 enabling CJK for LaTeX builder
> Apr 08 16:48:46 CC kernel/power/poweroff.o
> make[1]: *** [Documentation/Makefile:81: htmldocs] Error 2
> make: *** [Makefile:1549: htmldocs] Error 2
> make: *** Waiting for unfinished jobs....
This is weird, to say the least. But I think the "python3.8" in the
message above says everything you need to know. If you're running with
an unreleased version of Python, it's not entirely surprising that you
might run into trouble with a complex package.
jon
next prev parent reply other threads:[~2020-04-08 19:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-08 11:37 Kernel build failed ...SPHINX extension error Bhaskar Chowdhury
2020-04-08 19:25 ` Jonathan Corbet [this message]
2020-04-08 23:34 ` Bhaskar Chowdhury
2020-08-09 13:23 ` Documentation: build failure with sphinx >= 3.0.0: exception: cannot import name 'c_funcptr_sig_re' from 'sphinx.domains.c' (was: Re: Kernel build failed ...SPHINX extension error) Salvatore Bonaccorso
2020-08-12 7:30 ` Documentation: build failure with sphinx >= 3.0.0: exception: cannot import name 'c_funcptr_sig_re' from 'sphinx.domains.c' Salvatore Bonaccorso
2020-08-12 8:21 ` Markus Heiser
2020-08-12 12:44 ` Markus Heiser
2020-08-12 13:18 ` Jonathan Corbet
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=20200408132505.52e595bc@lwn.net \
--to=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=unixbhaskar@gmail.com \
/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.