On Sat, 8 Feb 2020 at 07:51, Markus Armbruster wrote:
> Peter Maydell writes:
> > It might be sphinx-build-3 on RH, but on Debian/Ubuntu it's
> > just 'sphinx-build' assuming you installed the python3-sphinx
> > and not the python2-sphinx, or you can run it directly out of
> > /usr/share/sphinx/s
Peter Maydell writes:
> On Fri, 7 Feb 2020 at 16:18, Markus Armbruster wrote:
>>
>> Peter Maydell writes:
>>
>> > Currently configure's has_sphinx_build() check simply runs a dummy
>> > sphinx-build and either passes or fails. This means that "no
>> > sphinx-build at all" and "sphinx-build exi
On Fri, 7 Feb 2020 at 16:18, Markus Armbruster wrote:
>
> Peter Maydell writes:
>
> > Currently configure's has_sphinx_build() check simply runs a dummy
> > sphinx-build and either passes or fails. This means that "no
> > sphinx-build at all" and "sphinx-build exists but is too old" are
> > both
Peter Maydell writes:
> Currently configure's has_sphinx_build() check simply runs a dummy
> sphinx-build and either passes or fails. This means that "no
> sphinx-build at all" and "sphinx-build exists but is too old" are
> both reported the same way.
>
> Further, we want to assume that all the
Currently configure's has_sphinx_build() check simply runs a dummy
sphinx-build and either passes or fails. This means that "no
sphinx-build at all" and "sphinx-build exists but is too old" are
both reported the same way.
Further, we want to assume that all the Python we write is running
with at
