From: Tom de Vries <tdevries@suse.de>
To: dwz@sourceware.org, jakub@redhat.com
Subject: [committed] Require hello-gnu-pubnames for pr24771.sh
Date: Tue, 01 Jan 2019 00:00:00 -0000 [thread overview]
Message-ID: <20190705173106.GA30917@delia> (raw)
Hi,
On the dwz-centos-* buildbots (apparantly with an older gcc) we see:
...
cc hello.c -o hello-gnu-pubnames -g -ggnu-pubnames
cc1: error: unrecognised debug output level "gnu-pubnames"
make: *** [hello-gnu-pubnames] Error 1
...
Fix this by allowing the hello-gnu-pubnames to fail, and requiring
hello-gnu-pubnames for pr24771.sh.
Committed to trunk.
Thanks,
- Tom
Require hello-gnu-pubnames for pr24771.sh
2019-07-05 Tom de Vries <tdevries@suse.de>
* Makefile (hello-gnu-pubnames): Allow compilation failure.
* testsuite/dwz.tests/dwz-tests.exp: Require hello-gnu-pubnames for
pr24771.sh.
---
Makefile | 2 +-
testsuite/dwz.tests/dwz-tests.exp | 3 +++
2 files changed, 4 insertions(+), 1 deletion(-)
diff --git a/Makefile b/Makefile
index 0216de4..f1214ba 100644
--- a/Makefile
+++ b/Makefile
@@ -33,7 +33,7 @@ hello:
$(CC) $(TEST_SRC)/hello.c -o $@ -g
hello-gnu-pubnames:
- $(CC) $(TEST_SRC)/hello.c -o $@ -g -ggnu-pubnames
+ $(CC) $(TEST_SRC)/hello.c -o $@ -g -ggnu-pubnames || touch $@
dw2-restrict:
$(CC) -no-pie $(TEST_SRC)/dw2-restrict.S -o $@ || touch $@
diff --git a/testsuite/dwz.tests/dwz-tests.exp b/testsuite/dwz.tests/dwz-tests.exp
index ad1ac47..9dda522 100644
--- a/testsuite/dwz.tests/dwz-tests.exp
+++ b/testsuite/dwz.tests/dwz-tests.exp
@@ -52,6 +52,9 @@ foreach test $tests {
if { $basename == "pr24747.sh" } {
lappend required_execs "start-gold"
}
+ if { $basename == "pr24771.sh" } {
+ lappend required_execs "hello-gnu-pubnames"
+ }
if { ![istarget x86_64-*-*] } {
if { $basename == "pr24468.sh" } {
unsupported "$test"
reply other threads:[~2019-07-05 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=20190705173106.GA30917@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).