From: Tom de Vries <tdevries@suse.de>
To: Tom Tromey <tromey@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 1/5] Remove gdb/testsuite/configure
Date: Sat, 7 Aug 2021 03:03:28 +0200 [thread overview]
Message-ID: <5d62daf3-7d0d-27cb-3c70-610dae53cbfe@suse.de> (raw)
In-Reply-To: <20210528192743.508390-2-tromey@adacore.com>
On 5/28/21 9:27 PM, Tom Tromey wrote:
> I didn't see a strong reason to have a separate configure script in
> gdb/testsuite, so this patch removes it.
FTR. AFAIU this has been reverted, but when building and testing
gdb-11-branch using an older snapshot still containing this change
(gdb-11.0.90.20210706.tar.xz), I ran into make check// no longer
working. The make target rule tests for [ -f testsuite/config.status ],
which is no longer generated after this patch.
Thanks,
- Tom
next prev parent reply other threads:[~2021-08-07 1:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-28 19:27 [PATCH 0/5] Some gdb build cleanups Tom Tromey
2021-05-28 19:27 ` [PATCH 1/5] Remove gdb/testsuite/configure Tom Tromey
2021-05-29 3:44 ` Simon Marchi
2021-06-01 13:59 ` Tom Tromey
2021-06-05 9:51 ` Tom de Vries
2021-06-09 14:35 ` Tom Tromey
2021-06-09 14:46 ` Tom de Vries
2021-08-07 1:03 ` Tom de Vries [this message]
2021-05-28 19:27 ` [PATCH 2/5] Always build 'all' in gdb/testsuite Tom Tromey
2021-05-28 19:27 ` [PATCH 3/5] Apply silent Makefile rules to gdb/testsuite Tom Tromey
2021-05-28 19:27 ` [PATCH 4/5] Clean up gdb's --enable-shared Tom Tromey
2021-05-28 19:27 ` [PATCH 5/5] Remove some gdb/data-directory special cases Tom Tromey
2021-05-29 3:50 ` [PATCH 0/5] Some gdb build cleanups Simon Marchi
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=5d62daf3-7d0d-27cb-3c70-610dae53cbfe@suse.de \
--to=tdevries@suse.de \
--cc=gdb-patches@sourceware.org \
--cc=tromey@adacore.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).