From: Nick Clifton <nickc@redhat.com>
To: Tom de Vries <tdevries@suse.de>, gdb-patches@sourceware.org
Cc: binutils@sourceware.org
Subject: Re: [RFC][top-level] Add configure test-case
Date: Mon, 31 Oct 2022 15:03:34 +0000 [thread overview]
Message-ID: <c628f170-8e05-c828-9ca1-68867641933c@redhat.com> (raw)
In-Reply-To: <20221020151027.GA1300@delia.home>
Hi Tom,
> I came up with a test-case named toplevel.exp, that can be run like this:
> ...
> $ cd src
> $ runtest toplevel.exp
Could it also be run as part of "make check" ?
> and leaves files $src/testrun.{log,sum}.
I would prefer the results to appear as $src/testsuite/toplevel.{log,sum},
ie in a directory of their own. I know that the ld and binutils testsuites
do not do this, but the gas one does, and so do the gcc testsuites.
I assume that you are also be suggesting this change on the gcc mailing list ?
Cheers
Nick
next prev parent reply other threads:[~2022-10-31 15:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 15:10 Tom de Vries
2022-10-31 15:03 ` Nick Clifton [this message]
2022-11-07 11:34 ` Alan Modra
2022-11-07 18:23 ` Joseph Myers
2022-11-08 7:12 ` Alan Modra
2023-01-14 8:51 ` Alexandre Oliva
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=c628f170-8e05-c828-9ca1-68867641933c@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@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).