tests/README: suggest how to run tests in cross-compile mode

* tests/README (Section "User interface" subsection "Running the
tests"): Briefly explain how to override 'host_alias' at runtime
to force the use of cross-compilers by the testsuite.  Give an
example.

diff --git a/ChangeLog b/ChangeLog
index fd23cb9..587490a 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,13 @@
 2011-05-21  Stefano Lattarini  <stefano.lattarini@gmail.com>
 
+       tests/README: suggest how to run tests in cross-compile mode
+       * tests/README (Section "User interface" subsection "Running the
+       tests"): Briefly explain how to override 'host_alias' at runtime
+       to force the use of cross-compilers by the testsuite.  Give an
+       example.
+
+2011-05-21  Stefano Lattarini  <stefano.lattarini@gmail.com>
+
        test defs: better detection of cross-compile mode
        * configure.ac (AC_CANONICAL_HOST): New, probably not strictly
        necessary, but useful to complements AC_CANONICAL_BUILD.

diff --git a/tests/README b/tests/README
index 29c964b..4d6bbf6 100644 (file)
--- a/tests/README
+++ b/tests/README
@@ -32,6 +32,19 @@ Running the tests
 
     env TESTS="foo.test bar.test" make -e -k check
 
+ To run the tests in cross-compilation mode:
+
+    make -k check host_alias="$host_alias"           (GNU make)
+    env host_alias="$host_alias" make -e -k check    (non-GNU make)
+
+ Here `$host_alias' should be defined to a proper value different from
+ configure-determined `$build_alias', and should refer to a set of
+ cross-compilers you have available on your system; for example, if
+ on Linux you have a set of MinGW-targeted cross-compilers named
+ 'i586-mingw32msvc-cc', 'i586-mingw32msvc-c++', etc., you could use:
+
+   make -k check host_alias='i586-mingw32msvc'
+
 
 Interpretation
 --------------