public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Vincent Smeets <Vincent.VSmeets@GMail.com>
To: gdb-patches@sourceware.org
Cc: Vincent Smeets <Vincent.VSmeets@GMail.com>
Subject: [PATCH 4/7] gold: build with mktemp
Date: Thu, 19 Jan 2023 18:55:04 +0100	[thread overview]
Message-ID: <20230119175507.25046-5-Vincent.VSmeets@GMail.com> (raw)
In-Reply-To: <20230119175507.25046-1-Vincent.VSmeets@GMail.com>

---
 gold/Makefile.am | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/gold/Makefile.am b/gold/Makefile.am
index 0999c5fc..ea0c1ede 100644
--- a/gold/Makefile.am
+++ b/gold/Makefile.am
@@ -247,8 +247,9 @@ install-exec-local: ld-new$(EXEEXT)
 POTFILES= $(CCFILES) $(HFILES) $(TARGETSOURCES)
 
 po/POTFILES.in: @MAINT@ Makefile
-	for f in $(POTFILES); do echo $$f; done | LC_ALL=C sort > tmp \
-	  && mv tmp $(srcdir)/po/POTFILES.in
+	tmp=`mktemp --tmpdir=. POTFILES.XXXXXX.in`; \
+	for f in $(POTFILES); do echo $$f; done | LC_ALL=C sort > $$tmp \
+	  && mv $$tmp $(srcdir)/po/POTFILES.in
 
 # Bootstrap test support.  We use ld-new to build ld1, then use ld1 to
 # build ld2.  ld1 and ld2 should be identical.  ld-new need not be
-- 
2.39.0


  parent reply	other threads:[~2023-01-19 17:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-19 17:55 [Bug binutils/30022] concurrent builds can fail Vincent Smeets
2023-01-19 17:55 ` [PATCH 1/7] bfd: build with mktemp Vincent Smeets
2023-01-19 17:55 ` [PATCH 2/7] binutils: " Vincent Smeets
2023-01-19 17:55 ` [PATCH 3/7] gas: " Vincent Smeets
2023-01-19 17:55 ` Vincent Smeets [this message]
2023-01-19 17:55 ` [PATCH 5/7] gprof: " Vincent Smeets
2023-01-19 17:55 ` [PATCH 6/7] ld: " Vincent Smeets
2023-01-19 17:55 ` [PATCH 7/7] opcodes: " Vincent Smeets
2023-01-19 20:32 ` [Bug binutils/30022] concurrent builds can fail Tom Tromey

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=20230119175507.25046-5-Vincent.VSmeets@GMail.com \
    --to=vincent.vsmeets@gmail.com \
    --cc=gdb-patches@sourceware.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).