From: Michael Chastain <mec.gnu@mindspring.com>
To: eliz@gnu.org
Cc: gdb-patches@sources.redhat.com
Subject: [patch/doco] test suite, build != host, version 2
Date: Fri, 20 Aug 2004 18:43:00 -0000 [thread overview]
Message-ID: <4126467C.nailG8P11SFWE@mindspring.com> (raw)
Version #2.
Testing: rebuilt gdb doco, it looked okay.
Okay to commit?
===
2004-08-20 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 20 Aug 2004 18:24:40 -0000
*************** difficult to test, such as code that han
*** 6279,6284 ****
--- 6279,6293 ----
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 build machine and
+ the host machine are not the same. In such an environment, these scripts
+ will give a result of ``UNRESOLVED'', like this:
+
+ @smallexample
+ UNRESOLVED: gdb.base/example.exp: This test script does not work on a remote host.
+ @end smallexample
+
@section Testsuite Organization
@cindex test suite organization
next reply other threads:[~2004-08-20 18:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-20 18:43 Michael Chastain [this message]
2004-08-21 9:31 ` Eli Zaretskii
2004-08-21 9:39 ` 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=4126467C.nailG8P11SFWE@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