This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [RFC] gdb/testsuite/gdb.exp not taking environment variable.


Cool! I will use --tool_exec instead. Is this documented some place? for
my future reference?

Thanks
----- ----
Manoj Iyer
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Cognito ergo sum                                                          +
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

On Thu, 29 Jul 2004, Michael Chastain wrote:

> Hi Manoj,
>
> TOOL_EXECUTABLE is not an environment variable.  It's a TCL variable
> which is initalized by runtest.exp in dejagnu, set by the
> "--tool_exec" flag.
>
> So the test-runner would say:
>
>   runtest --tool_exec /path/path/my_gdb ...
>
> And not: "export TOOL_EXECUTABLE=/path/path/my_gdb ; make check".
>
> You can do this at the 'make check' level with:
>
>   make check RUNTESTFLAGS="--tool_exec /path/path/my_gdb"
>
> Or:
>
>   export RUNTESTFLAGS="--tool_exec /path/path/my_gdb"
>   make -e check
>
> I don't want gdb/lib.exp to change the interface of an existing
> variable name which is imported from runtest.exp.
>
> Michael C
>


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]