Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Chastain <mec.gnu@mindspring.com>
To: gdb-patches@sources.redhat.com, eliz@gnu.org
Subject: [rfa/doco] Test Suite: build != host
Date: Thu, 19 Aug 2004 09:48:00 -0000	[thread overview]
Message-ID: <4124776A.nailCD81LG97@mindspring.com> (raw)

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


             reply	other threads:[~2004-08-19  9:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-19  9:48 Michael Chastain [this message]
2004-08-19  9:56 ` Andreas Schwab
2004-08-20 15:00   ` Eli Zaretskii
2004-08-20 15:07     ` Michael Chastain
2004-08-20 16:34       ` Eli Zaretskii
2004-08-19 13:21 ` Daniel Jacobowitz
2004-08-19 16:07   ` 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=4124776A.nailCD81LG97@mindspring.com \
    --to=mec.gnu@mindspring.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sources.redhat.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