public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: elfutils-devel@sourceware.org
Cc: Mark Wielaard <mark@klomp.org>
Subject: [COMMITTED] rpmbuild: fix Makefile rules
Date: Tue, 14 Nov 2023 00:53:06 +0100	[thread overview]
Message-ID: <20231113235306.1727664-1-mark@klomp.org> (raw)

	* Makefile.am (rpmbuild): Use mkdir -p. Use $(shell pwd).
---
 Makefile.am | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Makefile.am b/Makefile.am
index 87debb48..c9d59d4a 100644
--- a/Makefile.am
+++ b/Makefile.am
@@ -47,9 +47,9 @@ rpm: dist
 	rpmbuild -ts elfutils-@PACKAGE_VERSION@.tar.bz2
 
 rpmbuild: dist
-	mkdir rpmbuild
+	mkdir -p rpmbuild
 	rpmbuild -ta elfutils-@PACKAGE_VERSION@.tar.bz2 \
-		--define "_topdir $(pwd)/rpmbuild"
+		--define "_topdir $(shell pwd)/rpmbuild"
 
 if GCOV
 
-- 
2.39.3


                 reply	other threads:[~2023-11-13 23:53 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=20231113235306.1727664-1-mark@klomp.org \
    --to=mark@klomp.org \
    --cc=elfutils-devel@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).