public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@pfeifer.com>
To: overseers@gcc.gnu.org
Cc: David Malcolm <dmalcolm@redhat.com>
Subject: /usr/bin/sphinx-1.0-build: Command not found
Date: Sat, 14 Mar 2020 23:46:45 +0100 (CET)	[thread overview]
Message-ID: <alpine.LSU.2.21.2003142338100.4184@anthias.pfeifer.com> (raw)

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.

Gerald

             reply	other threads:[~2020-03-14 22:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-14 22:46 Gerald Pfeifer [this message]
2020-03-15  1:46 ` David Malcolm
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=alpine.LSU.2.21.2003142338100.4184@anthias.pfeifer.com \
    --to=gerald@pfeifer.com \
    --cc=dmalcolm@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).