public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Jeff Law <law@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r14-158] configure: Only create serdep.tmp if needed Date: Fri, 21 Apr 2023 19:16:14 +0000 (GMT) [thread overview] Message-ID: <20230421191614.D49DA3858D20@sourceware.org> (raw) https://gcc.gnu.org/g:7d115e014111565653b3e716bb2911c0016838e5 commit r14-158-g7d115e014111565653b3e716bb2911c0016838e5 Author: Peter Foley <pefoley2@pefoley.com> Date: Fri Apr 21 13:14:51 2023 -0600 configure: Only create serdep.tmp if needed 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 Diff: --- configure | 2 ++ configure.ac | 2 ++ 2 files changed, 4 insertions(+) diff --git a/configure b/configure index 85883099410..0494e2fa2bf 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 test "x${enable_serial_build_configure}" = xyes || test "x${enable_serial_host_configure}" = xyes || test "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..f5cce5830bc 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 test "x${enable_serial_build_configure}" = xyes || test "x${enable_serial_host_configure}" = xyes || test "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
reply other threads:[~2023-04-21 19:16 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=20230421191614.D49DA3858D20@sourceware.org \ --to=law@gcc.gnu.org \ --cc=gcc-cvs@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: linkBe 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).