From: Mike Frysinger <vapier@gentoo.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: gdb@sourceware.org, binutils@sourceware.org
Subject: Re: testsuite layout conventions
Date: Wed, 6 Jan 2021 05:09:54 -0500 [thread overview]
Message-ID: <20210106100954.GD7494@vapier> (raw)
In-Reply-To: <87im8aa2i3.fsf@linux-m68k.org>
[-- Attachment #1: Type: text/plain, Size: 933 bytes --]
On 06 Jan 2021 09:33, Andreas Schwab wrote:
> On Jan 06 2021, Mike Frysinger via Binutils wrote:
> > the odd thing is that it seems most projects don't actually set
> > tool in their site.exp. libstdc++, gdb, and sim do. so i guess
> > either the others ones used to, or they just adopted a similar
> > naming convention at some point because others were ?
>
> It can also be set on the command line. This is used by automake.
ah, thanks, i missed the projects using newer automake & DEJATOOL and
passing --tool to runtest directly rather than through site.exp. i
had expected site.exp so people could run `runtest` manually, but i
guess that's not really a common or supported flow. people only run
`make check` and such and never get lower.
i'm still stuck in the old Makefile.in world -- it still feels cutting
edge that binutils/gdb is using Makefile.am at all as i thought it'd
never happen ;).
-mike
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-01-06 10:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 5:12 Mike Frysinger
2021-01-06 8:33 ` Andreas Schwab
2021-01-06 10:09 ` Mike Frysinger [this message]
2021-01-06 10:49 ` Alan Modra
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=20210106100954.GD7494@vapier \
--to=vapier@gentoo.org \
--cc=binutils@sourceware.org \
--cc=gdb@sourceware.org \
--cc=schwab@linux-m68k.org \
/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).