From: Mark Wielaard <mark@klomp.org>
To: Tom de Vries <tdevries@suse.de>
Cc: dwz@sourceware.org
Subject: Re: Added a buildbot for dwz
Date: Tue, 01 Jan 2019 00:00:00 -0000 [thread overview]
Message-ID: <20190316175245.GB2435@wildebeest.org> (raw)
In-Reply-To: <defa4ba1-ae02-de69-ba80-2b62ec7178a5@suse.de>
[-- Attachment #1: Type: text/plain, Size: 1170 bytes --]
On Sat, Mar 16, 2019 at 05:37:34PM +0100, Tom de Vries wrote:
> On 16-03-19 17:31, Mark Wielaard wrote:
> > The following seems to always suppress the WARNING:
> >
> > diff --git a/Makefile b/Makefile
> > index 1aa208f..2a9898c 100644
> > --- a/Makefile
> > +++ b/Makefile
> > @@ -26,9 +26,14 @@ hello:
> > dw2-restrict:
> > $(CC) $(TEST_SRC)/dw2-restrict.S -o $@ || touch $@
> >
> > +# On some systems we need to set and export DEJAGNU to suppress
> > +# WARNING: Couldn't find the global config file.
> > +DEJAGNU ?= /dev/null
> > +
> > check: dwz $(TEST_EXECS)
> > mkdir -p testsuite-bin
> > cd testsuite-bin; ln -sf $(PWD)/dwz .
> > + export DEJAGNU=$(DEJAGNU); \
> > export PATH=$(PWD)/testsuite-bin:$$PATH; export LC_ALL=C; \
> > runtest --tool=dwz -srcdir testsuite $(RUNTESTFLAGS)
> > rm -Rf testsuite-bin $(TEST_EXECS)
> >
> > Does that make sense?
>
> Works for me.
Great. Pushed as attached.
On all buildbot workers make check is warning free.
On some there are some warnings about hashtab.c (implicit-fallthrough).
If that file comes from libiberty maybe we can simply remerge it?
Cheers,
Mark
[-- Attachment #2: 0001-export-DEJAGNU-for-make-check-to-suppress-global-con.patch --]
[-- Type: text/x-diff, Size: 1138 bytes --]
From f31e9dee0a45d392fe08d3441dd64200a5505a05 Mon Sep 17 00:00:00 2001
From: Mark Wielaard <mark@klomp.org>
Date: Sat, 16 Mar 2019 18:38:49 +0100
Subject: [PATCH] export DEJAGNU for make check to suppress global config file
WARNING.
On some systems we need to set and export DEJAGNU to suppress
WARNING: Couldn't find the global config file.
2019-03-16 Mark Wielaard <mark@klomp.org>
* Makefile (DEJAGNU): Optionally set variable.
(check): export DEJAGNU.
---
Makefile | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/Makefile b/Makefile
index 1aa208f..2ce7b59 100644
--- a/Makefile
+++ b/Makefile
@@ -26,9 +26,14 @@ hello:
dw2-restrict:
$(CC) $(TEST_SRC)/dw2-restrict.S -o $@ || touch $@
+# On some systems we need to set and export DEJAGNU to suppress
+# WARNING: Couldn't find the global config file.
+DEJAGNU ?= /dev/null
+
check: dwz $(TEST_EXECS)
mkdir -p testsuite-bin
cd testsuite-bin; ln -sf $(PWD)/dwz .
+ export DEJAGNU=$(DEJAGNU); \
export PATH=$(PWD)/testsuite-bin:$$PATH; export LC_ALL=C; \
runtest --tool=dwz -srcdir testsuite $(RUNTESTFLAGS)
rm -Rf testsuite-bin $(TEST_EXECS)
--
2.20.1
next prev parent reply other threads:[~2019-03-16 17:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 0:00 Tom de Vries
2019-01-01 0:00 ` Mark Wielaard
2019-01-01 0:00 ` Tom de Vries
2019-01-01 0:00 ` Mark Wielaard [this message]
2019-01-01 0:00 ` [PATCH] Backport "libiberty: Fix -Wimplicit-fallthrough warnings" Tom de Vries
2019-01-01 0:00 ` Jakub Jelinek
-- strict thread matches above, loose matches on Subject: below --
2019-01-01 0:00 Added a buildbot for dwz Mark Wielaard
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=20190316175245.GB2435@wildebeest.org \
--to=mark@klomp.org \
--cc=dwz@sourceware.org \
--cc=tdevries@suse.de \
/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).