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.
This commit is contained in:
parent
11003ae340
commit
e7dc800a0c
2 changed files with 14 additions and 0 deletions
|
@ -1,3 +1,8 @@
|
|||
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.
|
||||
|
||||
2004-08-14 Mark Kettenis <kettenis@gnu.org>
|
||||
|
||||
* gdbint.texinfo (Host Definition): Delete description of
|
||||
|
|
|
@ -6279,6 +6279,15 @@ difficult to test, such as code that handles host OS failures or bugs
|
|||
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
|
||||
|
|
Loading…
Reference in a new issue