From: Doug Evans <dje@google.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Pedro Alves <palves@redhat.com>,
Simon Marchi <simon.marchi@ericsson.com>,
gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Remove symlinks created in argv0-symlink.exp and general cleanup
Date: Tue, 11 Aug 2015 17:36:00 -0000 [thread overview]
Message-ID: <CADPb22TsqOiq6AM9h_0A-a7rp=dX6ds-E8K21goX+AK5UMjadA@mail.gmail.com> (raw)
In-Reply-To: <20150804172110.GI4777@adacore.com>
On Tue, Aug 4, 2015 at 10:21 AM, Joel Brobecker <brobecker@adacore.com> wrote:
>> Personally, I'd vote for making in-tree builds, or at least testing,
>> officially unsupported. I think gcc already does so...
>
> We should seriously discuss this, one day, as we keep having to
> spend time fixing issues specific to that mode.
I don't have a strong opinion on making in-tree testing unsupported,
but I do have a strong opinion on another thing that can make the
in-tree testing issue moot.
Let's remove all of testsuite/*/Makefile.in, they're always
out of date anyway (i.e., no one updates gdb.foo/Makefile.in to
remove binaries added by new tests),
and except for "make clean" aren't really used for anything.
The "make clean" in testsuite/Makefile.in can just "rm -rf foo bar ..."
[where "foo bar ..." are *not* the gdb.* testsuite dirs, but rather
the outputs,etc. directories of check-parallel]
IOW, testing would create the needed directories on the fly,
even in serial mode,
and to simplify "make clean" they'd always be put in a fixed
subdir of testsuite (just like check-parallel does now).
As for whether to always have one directory per test
(in serial and parallel modes), that *could* be treated as a separate
issue, but if it reduces complexity by doing the same thing
for serial and parallel then great.
[And while in-tree testing could still be unsupported,
I think(!) the current issue with it would be fixed.]
next prev parent reply other threads:[~2015-08-11 17:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 20:13 Simon Marchi
2015-08-03 14:23 ` Pedro Alves
2015-08-03 15:16 ` Simon Marchi
2015-08-03 16:34 ` Pedro Alves
2015-08-03 16:38 ` Pedro Alves
2015-08-03 18:10 ` Simon Marchi
2015-08-03 18:42 ` Pedro Alves
2015-08-04 16:11 ` Sergio Durigan Junior
2015-08-04 17:21 ` Joel Brobecker
2015-08-11 17:36 ` Doug Evans [this message]
2015-08-11 19:58 ` Joel Brobecker
2015-08-11 20:43 ` Doug Evans
2015-08-11 23:02 ` Joel Brobecker
2015-08-12 9:30 ` Pedro Alves
2015-08-12 16:40 ` Sergio Durigan Junior
2015-08-12 17:22 ` Joel Brobecker
2015-08-12 17:38 ` Doug Evans
2015-08-12 18:43 ` Joel Brobecker
2015-08-12 18:50 ` Doug Evans
2015-08-12 19:41 ` Joel Brobecker
2015-08-12 20:23 ` 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='CADPb22TsqOiq6AM9h_0A-a7rp=dX6ds-E8K21goX+AK5UMjadA@mail.gmail.com' \
--to=dje@google.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=simon.marchi@ericsson.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