Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
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 20:43:00 -0000	[thread overview]
Message-ID: <CADPb22Ty0KPD4M+WAv=9hc6dGEo8M0j7H=wh3K9M6hJsoc-Vew@mail.gmail.com> (raw)
In-Reply-To: <20150811195814.GB22245@adacore.com>

On Tue, Aug 11, 2015 at 12:58 PM, Joel Brobecker <brobecker@adacore.com> wrote:
>> 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).
>
> I think some of these issues are worth improving independently
> of whether the build was in-tree or not.
>
>> 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.]
>
> If in-tree build happens to work without effort from us, then
> OK to continue having it. But I don't think treating as bugs
> issues that are specific to in-tree building & testing would
> be the best investment of our resources.
>
> I tried to remember why people thought in-tree building is more
> convenient for them, and couldn't remember of any reason other
> than convenience. But is it really more convenient? Are there
> other reasons I forgot about?

FAOD, I'm *not* advocating for keeping in-tree builds working.
I never do them myself so I really have no direct interest in whether
it works or not. But, if something I want to do anyway happens
to improve life for someone else, then I'm ok with that.


  reply	other threads:[~2015-08-11 20:43 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
2015-08-11 19:58           ` Joel Brobecker
2015-08-11 20:43             ` Doug Evans [this message]
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='CADPb22Ty0KPD4M+WAv=9hc6dGEo8M0j7H=wh3K9M6hJsoc-Vew@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