From: Doug Evans <dje@google.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Tom Tromey <tromey@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [patch] Fix parallel gdb/ make check//% site.exp
Date: Mon, 09 Nov 2009 17:33:00 -0000 [thread overview]
Message-ID: <e394668d0911090933p1c15ffbdqbff5b23772f8aed6@mail.gmail.com> (raw)
In-Reply-To: <20091109171950.GA6665@host0.dyn.jankratochvil.net>
On Mon, Nov 9, 2009 at 9:19 AM, Jan Kratochvil
<jan.kratochvil@redhat.com> wrote:
>
> gdb/testsuite/
> 2009-11-09 Jan Kratochvil <jan.kratochvil@redhat.com>
>
> * Makefile.in (abs_builddir): New.
> (site.exp): New target `$(abs_builddir)/site.exp'. New comment.
> (check-single, $(TEST_TARGETS), check-gdb.base%): Change `site.exp' to
> `$(abs_builddir)/site.exp'.
>
> --- a/gdb/testsuite/Makefile.in
> +++ b/gdb/testsuite/Makefile.in
> @@ -22,6 +22,7 @@ VPATH = @srcdir@
> srcdir = @srcdir@
> prefix = @prefix@
> exec_prefix = @exec_prefix@
> +abs_builddir = @abs_builddir@
>
> target_alias = @target_noncanonical@
> program_transform_name = @program_transform_name@
> @@ -102,7 +103,11 @@ install:
>
> uninstall: force
>
> -site.exp: ./config.status Makefile
> +# Use absolute `site.exp' path everywhere to suppress VPATH lookups for it.
> +# $(RUNTEST) is looking up `site.exp' only in the current directory.
> +# Bare `site.exp' is present as a target here if user requests it explicitly.
> +
> +$(abs_builddir)/site.exp site.exp: ./config.status Makefile
> @echo "Making a new config file..."
> -@rm -f ./tmp?
> @touch site.exp
> @@ -147,7 +151,7 @@ DO_RUNTEST = \
> export TCL_LIBRARY ; fi ; \
> $(RUNTEST)
>
> -check-single: all site.exp
> +check-single: all $(abs_builddir)/site.exp
> $(DO_RUNTEST) $(RUNTESTFLAGS)
>
> # A list of all directories named "gdb.*" which also hold a .exp file.
> @@ -170,7 +174,7 @@ check-parallel:
> $(SHELL) $(srcdir)/dg-extract-results.sh -L \
> $(addsuffix /gdb.log,$(TEST_DIRS)) > gdb.log
>
> -$(filter-out check-gdb.base%,$(TEST_TARGETS)): check-gdb.%: all site.exp
> +$(filter-out check-gdb.base%,$(TEST_TARGETS)): check-gdb.%: all $(abs_builddir)/site.exp
> @if test ! -d gdb.$*; then mkdir gdb.$*; fi
> $(DO_RUNTEST) --directory=gdb.$* --outdir=gdb.$* $(RUNTESTFLAGS)
>
> @@ -179,7 +183,7 @@ BASE1_FILES = $(patsubst $(srcdir)/%,%,$(wildcard $(srcdir)/gdb.base/[a-m]*.exp)
> BASE2_FILES = $(patsubst $(srcdir)/%,%,$(wildcard $(srcdir)/gdb.base/[n-z]*.exp))
>
> # Handle each half of gdb.base.
> -check-gdb.base%: all site.exp
> +check-gdb.base%: all $(abs_builddir)/site.exp
> @if test ! -d gdb.base$*; then mkdir gdb.base$*; fi
> $(DO_RUNTEST) $(BASE$*_FILES) --outdir gdb.base$* $(RUNTESTFLAGS)
>
>
Thanks.
I didn't know about abs_builddir. At Cygnus we had a general rule of
keeping trees configured with relative paths movable, and I always
forget whether we care about that anymore.
OOC, does that impinge on this or do we no longer care about such things?
next prev parent reply other threads:[~2009-11-09 17:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-09 12:15 Jan Kratochvil
2009-11-09 15:37 ` Tom Tromey
2009-11-09 17:20 ` Jan Kratochvil
2009-11-09 17:32 ` Tom Tromey
2009-11-09 18:00 ` Jan Kratochvil
2009-11-09 17:33 ` Doug Evans [this message]
2009-11-09 17:50 ` Jan Kratochvil
2009-11-09 17:53 ` Daniel Jacobowitz
2009-11-09 16:38 ` Doug Evans
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=e394668d0911090933p1c15ffbdqbff5b23772f8aed6@mail.gmail.com \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=tromey@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