public inbox for dwz@sourceware.org
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: dwz@sourceware.org, jakub@redhat.com
Subject: [committed] Fix dwz-for-test sources
Date: Tue, 01 Jan 2019 00:00:00 -0000	[thread overview]
Message-ID: <20190318173216.GA17702@delia> (raw)

Hi,

Currently dwz-for-test is compiled using $(OBJECTS) instead of the
corresponding sources files.

Fix this by fixing the patsubst function call.

Committed to trunk.

Thanks,
- Tom

Fix dwz-for-test sources

2019-03-18  Tom de Vries  <tdevries@suse.de>

	* Makefile (dwz-for-test): Fix sources.

---
 Makefile | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Makefile b/Makefile
index d2aa386..0f47a98 100644
--- a/Makefile
+++ b/Makefile
@@ -30,7 +30,7 @@ py-section-script:
 	$(CC) $(TEST_SRC)/py-section-script.s -o $@ -g || touch $@
 
 dwz-for-test:
-	$(CC) $(patsubst \.o$,.c,$(OBJECTS)) -O2 -g -w -lelf -o $@ -W \
+	$(CC) $(patsubst %.o,%.c,$(OBJECTS)) -O2 -g -w -lelf -o $@ -W \
 	  -D_FILE_OFFSET_BITS=64 -DDWZ_VERSION='"for-test"'
 
 # On some systems we need to set and export DEJAGNU to suppress

                 reply	other threads:[~2019-03-18 17:31 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=20190318173216.GA17702@delia \
    --to=tdevries@suse.de \
    --cc=dwz@sourceware.org \
    --cc=jakub@redhat.com \
    /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).