From: Peter Foley <pefoley2@pefoley.com>
To: gcc-patches@gcc.gnu.org
Cc: Peter Foley <pefoley2@pefoley.com>
Subject: [PATCH] configure: Only create serdep.tmp if needed
Date: Sun, 15 Jan 2023 00:58:42 -0500 [thread overview]
Message-ID: <20230115055842.3965247-1-pefoley2@pefoley.com> (raw)
There's no reason to create this file if none of the serial configure
options are passed.
ChangeLog:
* configure: Regenerate.
* configure.ac: Only create serdep.tmp if needed
Signed-off-by: Peter Foley <pefoley2@pefoley.com>
---
configure | 2 ++
configure.ac | 2 ++
2 files changed, 4 insertions(+)
diff --git a/configure b/configure
index 85883099410..47caaeb23fe 100755
--- a/configure
+++ b/configure
@@ -9918,7 +9918,9 @@ esac
# These force 'configure's to be done one at a time, to avoid problems
# with contention over a shared config.cache.
rm -f serdep.tmp
+if "x${enable_serial_build_configure}" = xyes || "x${enable_serial_host_configure}" = xyes || "x${enable_serial_target_configure}" = xyes ; then
echo '# serdep.tmp' > serdep.tmp
+fi
olditem=
test "x${enable_serial_build_configure}" = xyes &&
for item in ${build_configdirs} ; do
diff --git a/configure.ac b/configure.ac
index 2b612dce6e9..847df0c99b5 100644
--- a/configure.ac
+++ b/configure.ac
@@ -3071,7 +3071,9 @@ esac
# These force 'configure's to be done one at a time, to avoid problems
# with contention over a shared config.cache.
rm -f serdep.tmp
+if [ "x${enable_serial_build_configure}" = xyes || "x${enable_serial_host_configure}" = xyes || "x${enable_serial_target_configure}" = xyes ]; then
echo '# serdep.tmp' > serdep.tmp
+fi
olditem=
test "x${enable_serial_build_configure}" = xyes &&
for item in ${build_configdirs} ; do
--
2.39.0
next reply other threads:[~2023-01-15 5:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-15 5:58 Peter Foley [this message]
2023-01-17 1:12 ` [PATCH v2] " Peter Foley
2023-01-17 1:14 ` Jeff Law
2023-04-21 19:16 ` Jeff Law
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=20230115055842.3965247-1-pefoley2@pefoley.com \
--to=pefoley2@pefoley.com \
--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).