From: Tom Tromey <tom@tromey.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] sim: common: modernize gennltvals.sh
Date: Wed, 20 Jan 2021 12:51:46 -0700 [thread overview]
Message-ID: <877do75qul.fsf@tromey.com> (raw)
In-Reply-To: <YAX6gNK+djvFwGsg@vapier> (Mike Frysinger via Gdb-patches's message of "Mon, 18 Jan 2021 16:15:44 -0500")
>> I think it would be perfectly fine to require bash or python.
Mike> in what context ? i assume it's off-limits for people downloading a
Mike> release and building e.g. gdb or gas. but is it acceptable for devs
Mike> doing dev work (which is what this thing is) ?
For the ordinary build, the normal rule is pretty restrictive. We can
rely on sh (the exact version isn't specified, but I suppose it is just
"whatever works on the subset of build machines we want to work"), and a
handful of standard Unix tools that are listed in the GNU Coding
Standards.
For maintainer stuff, I think anything goes. We already rely on Perl
(see make-target-delegates) and Tcl (via dejagnu) and Python
(contrib/dg-extract-results.py).
Probably we should not include things using obscure languages. Even for
the Perl script there was a complaint.
Tom
next prev parent reply other threads:[~2021-01-20 19:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-17 10:10 Mike Frysinger via Gdb-patches
2021-01-17 10:36 ` [PATCH] sim: common: delete configure & Makefile Mike Frysinger via Gdb-patches
2021-01-18 10:01 ` Andrew Burgess
2021-01-18 10:00 ` [PATCH] sim: common: modernize gennltvals.sh Andrew Burgess
2021-01-18 17:09 ` Mike Frysinger via Gdb-patches
2021-01-18 14:04 ` Simon Marchi via Gdb-patches
2021-01-18 17:13 ` Mike Frysinger via Gdb-patches
2021-01-18 17:19 ` Simon Marchi via Gdb-patches
2021-01-18 17:52 ` Mike Frysinger via Gdb-patches
2021-01-18 18:08 ` Simon Marchi via Gdb-patches
2021-01-18 21:15 ` Mike Frysinger via Gdb-patches
2021-01-18 21:27 ` Simon Marchi via Gdb-patches
2021-01-20 19:51 ` Tom Tromey [this message]
2021-01-18 17:20 ` [PATCH v2] " Mike Frysinger via Gdb-patches
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=877do75qul.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
/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