public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Janis Johnson <janis187@us.ibm.com>
To: David Edelsohn <dje@watson.ibm.com>
Cc: Janis Johnson <janis187@us.ibm.com>,
	Stephen Biggs <xyzzy@hotpop.com>, GCC list <gcc@gcc.gnu.org>
Subject: Re: Testsuite custom environment
Date: Tue, 20 May 2003 22:00:00 -0000	[thread overview]
Message-ID: <20030520144141.A27221@us.ibm.com> (raw)
In-Reply-To: <200305202115.RAA30208@makai.watson.ibm.com>; from dje@watson.ibm.com on Tue, May 20, 2003 at 05:15:56PM -0400

On Tue, May 20, 2003 at 05:15:56PM -0400, David Edelsohn wrote:
> >>>>> Janis Johnson writes:
> 
> Janis> I've tried lots of different ways to get a variable passed through to
> Janis> the testing tools and haven't yet figured out how to do it.  For the
> Janis> binary compatibility tests I gave up and had the Makefile write
> Janis> particular variables to site.exp; ugly, but it did what I needed.  If
> Janis> there's a better way to do this, I'd like to know about it, too, and
> Janis> then we can fix the documentation.
>  
> Are
> 
> 	--tool_opts
> 
> and 
> 	RUNTESTFLAGS=""
> 
> useful?
> 
> 	--tool_opts can specify additional options that always are applied
> to the commandline when invoking the tool, but not overriding existing
> flags.
> 
> 	RUNTESTFLAGS can specify those options in an environment variable,
> e.g., when running from "make check".

RUNTESTFLAGS is used to pass options to runtest; the list of those
options can be seen with runtest --help.  I've used --tool-opts to
specify flags that are passed to the compiler (the "tool") for every
invocation, but haven't figured out how to set environment variables
that will be recognized by the .exp files.  I suppose it would help
to read the documentation for expect.

Janis

  reply	other threads:[~2003-05-20 21:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-20 16:34 Stephen Biggs
2003-05-20 18:42 ` Richard Sandiford
2003-05-20 20:51 ` Janis Johnson
2003-05-20 21:38   ` David Edelsohn
2003-05-20 22:00     ` Janis Johnson [this message]
2003-05-20 22:08       ` Janis Johnson
2003-05-20 23:23         ` Mike Stump
2003-06-03  7:51           ` Stephen Biggs

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=20030520144141.A27221@us.ibm.com \
    --to=janis187@us.ibm.com \
    --cc=dje@watson.ibm.com \
    --cc=gcc@gcc.gnu.org \
    --cc=xyzzy@hotpop.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).