qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>, John Snow <jsnow@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: Building of docs does not work anymore
Date: Wed, 7 Jun 2023 11:46:08 +0200	[thread overview]
Message-ID: <c21f16ae-f653-4150-1372-b33f99342bf2@redhat.com> (raw)
In-Reply-To: <b869ab5c-7b2f-93fc-678f-53ee39118f97@redhat.com>

On 07/06/2023 11.42, Thomas Huth wrote:
> 
>   Hi Paolo, hi John,
> 
> since the recent reworks with the Python venv, building of the docs does not 
> work for me on my RHEL 8 installation anymore.
> 
> If I just run "configure" without any additional arguments, I get:
> 
> ------------------------- 8< -----------------------------
> $ ./configure
> Using './build' as the directory for build output
> python determined to be '/usr/bin/python3.8'
> python version: Python 3.8.13
> mkvenv: Creating non-isolated virtual environment at 'pyvenv'
> mkvenv: checking for meson>=0.63.0
> mkvenv: installing meson>=0.63.0
> mkvenv: checking for sphinx>=1.6.0, sphinx-rtd-theme>=0.5.0
> 
> *** Ouch! ***
> 
> Could not provide build dependency 'sphinx>=1.6.0':
>   • Python package 'sphinx' was not found nor installed.
>   • mkvenv was configured to operate offline and did not check PyPI.
>   • 'sphinx-build' was detected on your system at '/usr/bin/sphinx-build', 
> but the Python package 'sphinx' was not found by this Python interpreter 
> ('/usr/bin/python3.8'). Typically this means that 'sphinx-build' has been 
> installed against a different Python interpreter on your system.
> 
> Sphinx not found/usable, disabling docs.
> ------------------------- 8< -----------------------------
> 
> If I enable downloads and enforce --enable-docs , I get:
> 
> ------------------------- 8< -----------------------------
> ./configure --enable-docs --enable-download
> Using './build' as the directory for build output
> python determined to be '/usr/bin/python3.8'
> python version: Python 3.8.13
> mkvenv: Creating non-isolated virtual environment at 'pyvenv'
> mkvenv: checking for meson>=0.63.0
> mkvenv: installing meson>=0.63.0
> mkvenv: checking for sphinx>=1.6.0, sphinx-rtd-theme>=0.5.0
> mkvenv: installing sphinx>=1.6.0, sphinx-rtd-theme>=0.5.0
> ERROR: sphinx-rtd-theme 1.2.1 has requirement docutils<0.19, but you'll have 
> docutils 0.20.1 which is incompatible.
> ERROR: sphinx-rtd-theme 1.2.1 has requirement sphinx<7,>=1.6, but you'll 
> have sphinx 7.0.1 which is incompatible.
> ------------------------- 8< -----------------------------

Actually, it seems like it builds the docs in the latter case ... but the 
two error messages still look quite menacing (printed with red letters).

  Thomas



  reply	other threads:[~2023-06-07  9:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-07  9:42 Building of docs does not work anymore Thomas Huth
2023-06-07  9:46 ` Thomas Huth [this message]
2023-06-08  0:04   ` John Snow

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=c21f16ae-f653-4150-1372-b33f99342bf2@redhat.com \
    --to=thuth@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).