Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Manoj Iyer <manjo@austin.ibm.com>
To: Michael Chastain <mec.gnu@mindspring.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] gdb/testsuite/gdb.exp not taking environment variable.
Date: Sat, 31 Jul 2004 00:23:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.58.0407301351150.29619@lazy> (raw)
In-Reply-To: <4109852E.nailAM721SQNX@mindspring.com>


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
>


  reply	other threads:[~2004-07-31  0:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-29 20:43 Manoj Iyer
2004-07-29 23:15 ` Michael Chastain
2004-07-31  0:23   ` Manoj Iyer [this message]
2004-07-31  2:12     ` Michael Chastain

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=Pine.LNX.4.58.0407301351150.29619@lazy \
    --to=manjo@austin.ibm.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mec.gnu@mindspring.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