From: David Malcolm <dmalcolm@redhat.com>
To: Gerald Pfeifer <gerald@pfeifer.com>, overseers@gcc.gnu.org
Cc: jakub@redhat.com
Subject: Re: /usr/bin/sphinx-1.0-build: Command not found
Date: Sat, 14 Mar 2020 21:46:16 -0400 [thread overview]
Message-ID: <02a6a5c8a7dd0b30502912c0eb6989d6a1a0615d.camel@redhat.com> (raw)
In-Reply-To: <alpine.LSU.2.21.2003142338100.4184@anthias.pfeifer.com>
On Sat, 2020-03-14 at 23:46 +0100, Gerald Pfeifer wrote:
> The crontab of the gccadmin account invokes
> /home/gccadmin/scripts/update_web_docs_git
> once a day.
>
> Presumably since the migration this has been failing as follows:
>
> Output written on libiberty.pdf (52 pages, 356199 bytes).
> Transcript written on libiberty.log.
> /tmp/gcc-doc-update.43504/gcc/gcc/jit/docs /tmp/gcc-doc-
> update.43504
> /usr/bin/sphinx-1.0-build -b html -d _build/doctrees .
> _build/html
> make: /usr/bin/sphinx-1.0-build: Command not found
> make: *** [Makefile:45: html] Error 127
> /tmp/gcc-doc-update.43504
> cp: cannot stat 'gcc/gcc/jit/docs/_build/html': No such file or
> directory
>
> The script currently has the following comment:
>
> # The jit is a special-case, using sphinx rather than texinfo.
> # Specifically, the jit docs need sphinx 1.0 or later.
> #
> # The jit/docs Makefile uses the executable $(SPHINXBUILD),
> # defaulting to "sphinx-build".
> #
> # sphinx is packaged in Fedora and EPEL 6 within "python-sphinx",
> # and in openSUSE within "python-Sphinx".
> #
> # For EPEL6, python-sphinx is sphinx 0.6.6, which is missing
> various
> # directives (e.g. ":c:macro:"), so we need the variant
> # python-sphinx10 package. The latter installs its executable as
> # /usr/bin/sphinx-1.0-build
> # so we need to override SPHINXBUILD with this when invoking
> "make".
>
> David (copied) contributed this piece, so may be able to help with
> any questions.
[CCing Jakub]
Jakub committed a patch for this on Thursday to the gcc repository:
https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=a0ae4cbe9d1430b32f674b862a6d8dce0ed81f2a
which I believe ought to fix it (assuming the box in question is now
running RHEL 8).
The mailing list discussion was here:
https://gcc.gnu.org/pipermail/gcc-patches/2020-March/541922.html
Does the updated script need to be copied over somewhere?
Dave
next prev parent reply other threads:[~2020-03-15 1:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-14 22:46 Gerald Pfeifer
2020-03-15 1:46 ` David Malcolm [this message]
2020-03-15 8:55 ` Gerald Pfeifer
2020-03-15 14:27 ` David Malcolm
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=02a6a5c8a7dd0b30502912c0eb6989d6a1a0615d.camel@redhat.com \
--to=dmalcolm@redhat.com \
--cc=gerald@pfeifer.com \
--cc=jakub@redhat.com \
--cc=overseers@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).