summaryrefslogtreecommitdiff
path: root/contrib/gcc-test-suite/README
diff options
context:
space:
mode:
authorYann E. MORIN" <yann.morin.1998@anciens.enib.fr>2010-05-22 20:04:31 (GMT)
committerYann E. MORIN" <yann.morin.1998@anciens.enib.fr>2010-05-22 20:04:31 (GMT)
commitdbd5e50583752baccb59d981c2e434d3e518f762 (patch)
treef10d3ddd27ab90e6799e209fe297644106c13aa0 /contrib/gcc-test-suite/README
parent1779c82ad2916f9a3c3ad2dd350dbeb2d6692f9d (diff)
test-suite: apply cleanup pass
Remove all non-modifiable items (target tuple, gcc version, toolchain path...) Makefile syntax ( use $(...) instead of ${...} ) Update doc Space-damage cleanups
Diffstat (limited to 'contrib/gcc-test-suite/README')
-rw-r--r--contrib/gcc-test-suite/README38
1 files changed, 25 insertions, 13 deletions
diff --git a/contrib/gcc-test-suite/README b/contrib/gcc-test-suite/README
index 99d61cc..0c81be9 100644
--- a/contrib/gcc-test-suite/README
+++ b/contrib/gcc-test-suite/README
@@ -7,7 +7,6 @@ Requirements
* DejaGnu 'runtest' v1.4.4+
* Make v3.81+
-* wget
Configuration
@@ -19,16 +18,23 @@ Alternatively, override configuration variables on the command line.
Available config variables:
-DG_GCC_VERSION
-DG_GCC_URL
DG_TOOLNAME
-DG_TARGET
+ The name of the tool you want to test.
+ Currently supported: gcc or g++
+ Default: gcc
+
DG_TARGET_HOSTNAME
+ The hostname or IP of the machine to execute run-tests
+ Default: 127.0.0.1
+
DG_TARGET_USERNAME
+ Execute the run-test as this user on DG_TARGET_HOSTNAME
+ Default: root
+
DG_C_TESTS
DG_CPP_TESTS
-DG_TOOLCHAIN_DIR
-DG_SRC_DIR
+ The C/C++ tests you want to check
+ Default: (empty, means all tests)
Run examples
@@ -53,19 +59,25 @@ SSH automatic login configuration example
On host do:
ssh-keygen -t rsa (then simply press enter thru all steps)
-scp ~/.ssh/id_rsa.pub <username>@<target IP>:~/
-
-On target do:
-cd ~
-mkdir .ssh
-cat id_rsa.pub >> .ssh/authorized_keys
-rm id_rsa.pub
+ssh-copy-id -i ~/.ssh/id_rsa.pub <username>@<target IP>
Now automatic ssh login should work - test by doing a simple ssh session to target.
Note: The procedure might be slightly different for your particular target.
+Getting rid of the test-suite
+-----------------------------
+
+If you no longer have a need for the test-suite, then you can remove it altogether
+from your toolchain. Just delete the test-suite/ dub-dir.
+
+
Author
------
Martin Lund <mgl@doredevelopment.dk>
+ Initial content
+
+"Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
+ Getting rid of the test-suite
+ Minor fixes