public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/107620] Build errors when using sphinx
Date: Sun, 13 Nov 2022 15:36:30 +0000	[thread overview]
Message-ID: <bug-107620-4-Clk74MUNYO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107620-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107620

--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Martin Liska <marxin@gcc.gnu.org>:

https://gcc.gnu.org/g:5e749ee3019d7917184af30dab8d09c933c0a4a1

commit r13-3940-g5e749ee3019d7917184af30dab8d09c933c0a4a1
Author: Martin Liska <mliska@suse.cz>
Date:   Sun Nov 13 15:07:17 2022 +0100

    configure: always set SPHINX_BUILD

    During the Sphinx-migration development, I used
    SPHINX_BUILD='' in order to skip building info and manual
    pages in gcc folder. However, we've got HAS_SPHINX_BUILD
    which is the correct flag for that.

    With the patch, one will get a nicer error message when
    sphinx-build is missing and one builds (explicitly) a target which
    depends on it.

            PR other/107620

    gcc/ChangeLog:

            * configure: Regenerate.
            * configure.ac: Always set sphinx-build.

    libgomp/ChangeLog:

            * configure: Regenerate.
            * configure.ac: Always set sphinx-build.

    libiberty/ChangeLog:

            * configure: Regenerate.
            * configure.ac: Always set sphinx-build.

    libitm/ChangeLog:

            * configure: Regenerate.
            * configure.ac: Always set sphinx-build.

    libquadmath/ChangeLog:

            * configure: Regenerate.
            * configure.ac: Always set sphinx-build.

  parent reply	other threads:[~2022-11-13 15:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-10 16:45 [Bug other/107620] New: " vvinayag at arm dot com
2022-11-11 15:56 ` [Bug other/107620] " marxin at gcc dot gnu.org
2022-11-12 18:38 ` vvinayag at arm dot com
2022-11-13 10:38 ` ramana at gcc dot gnu.org
2022-11-13 15:36 ` cvs-commit at gcc dot gnu.org [this message]
2022-11-13 15:37 ` marxin at gcc dot gnu.org
2022-11-13 15:38 ` marxin at gcc dot gnu.org

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=bug-107620-4-Clk74MUNYO@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).