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]

[rfa/doco] Test Suite: build != host


This patch documents that the gdb test suite is supported with
build != host, but that some test scripts do not work and
will return UNRESOLVED if build != host.

I don't know if "UNRESOLVED" needs some kind of @foo{...}
markup.

Testing: rebuilt gdb doco, it looked okay.

Okay to commit?

Michael

===

2004-08-19  Michael Chastain  <mec.gnu@mindspring.com>

	* (Using the Testsuite): build != host is supported,
	but some test scripts do not support build != host.

Index: gdbint.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdbint.texinfo,v
retrieving revision 1.219
diff -c -3 -p -r1.219 gdbint.texinfo
*** gdbint.texinfo	14 Aug 2004 21:11:43 -0000	1.219
--- gdbint.texinfo	19 Aug 2004 08:59:19 -0000
*************** difficult to test, such as code that han
*** 6279,6284 ****
--- 6279,6289 ----
  in particular versions of compilers, and it's OK not to try to write
  tests for all of those.
  
+ DejaGNU supports separate build, host, and target machines.  However,
+ some @value{GDBN} test scripts do not work if the host machine is
+ separate from the build machine.  These scripts will return an
+ UNRESOLVED result in such an environment.
+ 
  @section Testsuite Organization
  
  @cindex test suite organization


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