public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Martin Liška" <mliska@suse.cz>
To: gcc-patches@gcc.gnu.org
Subject: [PATCH (pushed)] sphinx: add missing HAS_SPHINX_BUILD
Date: Wed, 9 Nov 2022 20:33:51 +0100	[thread overview]
Message-ID: <97cc7812-2e50-7965-3cb1-31ce1f82ea70@suse.cz> (raw)

libgomp/ChangeLog:

	* Makefile.in: Add missing HAS_SPHINX_BUILD.

libitm/ChangeLog:

	* Makefile.in: Add missing HAS_SPHINX_BUILD.

libquadmath/ChangeLog:

	* Makefile.in: Add missing HAS_SPHINX_BUILD.
---
 libgomp/Makefile.in     | 1 +
 libitm/Makefile.in      | 1 +
 libquadmath/Makefile.in | 1 +
 3 files changed, 3 insertions(+)

diff --git a/libgomp/Makefile.in b/libgomp/Makefile.in
index 0c016980c3d..814ccd13dc0 100644
--- a/libgomp/Makefile.in
+++ b/libgomp/Makefile.in
@@ -401,6 +401,7 @@ SED = @SED@
 SET_MAKE = @SET_MAKE@
 SHELL = @SHELL@
 SPHINX_BUILD = @SPHINX_BUILD@
+HAS_SPHINX_BUILD = @HAS_SPHINX_BUILD@
 STRIP = @STRIP@
 VERSION = @VERSION@
 XCFLAGS = @XCFLAGS@
diff --git a/libitm/Makefile.in b/libitm/Makefile.in
index f51858db8c7..a07b9ebc6d0 100644
--- a/libitm/Makefile.in
+++ b/libitm/Makefile.in
@@ -347,6 +347,7 @@ SED = @SED@
 SET_MAKE = @SET_MAKE@
 SHELL = @SHELL@
 SPHINX_BUILD = @SPHINX_BUILD@
+HAS_SPHINX_BUILD = @HAS_SPHINX_BUILD@
 STRIP = @STRIP@
 VERSION = @VERSION@
 XCFLAGS = @XCFLAGS@
diff --git a/libquadmath/Makefile.in b/libquadmath/Makefile.in
index 864ebc6048a..10e402ccd07 100644
--- a/libquadmath/Makefile.in
+++ b/libquadmath/Makefile.in
@@ -347,6 +347,7 @@ SED = @SED@
 SET_MAKE = @SET_MAKE@
 SHELL = @SHELL@
 SPHINX_BUILD = @SPHINX_BUILD@
+HAS_SPHINX_BUILD = @HAS_SPHINX_BUILD@
 STRIP = @STRIP@
 VERSION = @VERSION@
 XCFLAGS = @XCFLAGS@
-- 
2.38.0


                 reply	other threads:[~2022-11-09 19:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=97cc7812-2e50-7965-3cb1-31ce1f82ea70@suse.cz \
    --to=mliska@suse.cz \
    --cc=gcc-patches@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).