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.

From: Michael Chastain <mec dot gnu at mindspring dot com>
To: manjo at austin dot ibm dot com
Cc: gdb-patches at sources dot redhat dot com
Date: Fri, 30 Jul 2004 22:12:33 -0400
Subject: Re: [RFC] gdb/testsuite/gdb.exp not taking environment variable.
References: <Pine.LNX.4.58.0407291512180.9771@lazy><4109852E.nailAM721SQNX@mindspring.com><Pine.LNX.4.58.0407301351150.29619@lazy>

Manoj Iyer <manjo@austin.ibm.com> wrote:
> Cool! I will use --tool_exec instead. Is this documented some place? for
> my future reference?

With dejagnu 1.4.4, it's not documented in 'man runtest', but it is
listed in 'runtest --help', and mentioned in doc/overview.ps and
doc/user.sgml in the dejagnu 1.4.4 doc/ subtree.

Also, by the way, dejagnu thinks that it is testing one tool at a time.
It doesn't understand that gdb needs to specify several other tools
as well (versions of gcc and binutils).  There is some confusion about
this in lib/java.exp where java_init uses TOOL_EXECUTABLE to initialize
GCJ_UNDER_TEST.  I need to fix that.  Until then, if you set
TOOL_EXECUTABLE, I think the Java tests will screw up.

Michael C

References:
- [RFC] gdb/testsuite/gdb.exp not taking environment variable.
  - From: Manoj Iyer
- Re: [RFC] gdb/testsuite/gdb.exp not taking environment variable.
  - From: Michael Chastain
- Re: [RFC] gdb/testsuite/gdb.exp not taking environment variable.
  - From: Manoj Iyer

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