From: Tom de Vries <tdevries@suse.de>
To: dwz@sourceware.org, jakub@redhat.com
Subject: [committed][testsuite] Fix make check CC="gcc -m32"
Date: Wed, 3 Feb 2021 11:12:44 +0100 [thread overview]
Message-ID: <20210203101243.GA25124@delia> (raw)
Hi,
When running:
...
$ make check CC="gcc -m32"
...
we run into:
...
gcc -m32 py-section-script.s -o py-section-script -g
py-section-script.s: Assembler messages:
py-section-script.s:53: Error: bad register name `%rbp'
...
make[1]: *** [Makefile:50: py-section-script] Error 1
...
Fix this by adding "|| touch $@" in the Makefile rule for this test-case (and
a few others), which makes the test unsupported.
Committed to trunk.
Thanks,
- Tom
[testsuite] Fix make check CC="gcc -m32"
2021-02-03 Tom de Vries <tdevries@suse.de>
* Makefile (dw2-skip-prologue, py-section-script)
(implptr-64bit-d2o4a8r8t0): Add "|| touch $@".
---
Makefile | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/Makefile b/Makefile
index 340569a..3fa3a27 100644
--- a/Makefile
+++ b/Makefile
@@ -44,10 +44,10 @@ hello-gnu-pubnames:
dw2-skip-prologue:
$(CC) $(TEST_SRC)/dw2-skip-prologue.S $(TEST_SRC)/dw2-skip-prologue.c \
- -DINLINED -DPTRBITS=64 -o $@
+ -DINLINED -DPTRBITS=64 -o $@ || touch $@
py-section-script:
- $(CC) $(TEST_SRC)/py-section-script.s -o $@ -g
+ $(CC) $(TEST_SRC)/py-section-script.s -o $@ -g || touch $@
DWZ_TEST_SOURCES := $(patsubst %.o,%-for-test.c,$(OBJECTS))
@@ -74,14 +74,14 @@ start-gold:
implptr-64bit-d2o4a8r8t0:
$(CC) $(TEST_SRC)/implptr-64bit-d2o4a8r8t0.S $(TEST_SRC)/main.c \
- -o $@ -g
+ -o $@ -g || touch $@
hello-gold-gdb-index:
$(CC) $(TEST_SRC)/hello.c -g -fuse-ld=gold -Wl,--gdb-index -o $@ \
|| touch $@
varval:
- $(CC) $(TEST_SRC)/varval.c $(TEST_SRC)/varval.S -g -o $@
+ $(CC) $(TEST_SRC)/varval.c $(TEST_SRC)/varval.S -g -o $@ || touch $@
POINTER_SIZE:=$(shell $(CC) $(TEST_SRC)/pointer-size.c -o pointer-size; \
./pointer-size; \
reply other threads:[~2021-02-03 10:12 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=20210203101243.GA25124@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).