This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Testsuite custom environment
- From: Janis Johnson <janis187 at us dot ibm dot com>
- To: David Edelsohn <dje at watson dot ibm dot com>
- Cc: Janis Johnson <janis187 at us dot ibm dot com>, Stephen Biggs <xyzzy at hotpop dot com>, GCC list <gcc at gcc dot gnu dot org>
- Date: Tue, 20 May 2003 14:41:41 -0700
- Subject: Re: Testsuite custom environment
- References: <janis187@us.ibm.com> <200305202115.RAA30208@makai.watson.ibm.com>
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