1.1 --- a/contrib/gcc-test-suite/README Wed May 19 17:53:04 2010 +0200
1.2 +++ b/contrib/gcc-test-suite/README Fri Aug 19 22:43:01 2011 +0200
1.3 @@ -7,7 +7,6 @@
1.4
1.5 * DejaGnu 'runtest' v1.4.4+
1.6 * Make v3.81+
1.7 -* wget
1.8
1.9
1.10 Configuration
1.11 @@ -19,16 +18,23 @@
1.12
1.13 Available config variables:
1.14
1.15 -DG_GCC_VERSION
1.16 -DG_GCC_URL
1.17 DG_TOOLNAME
1.18 -DG_TARGET
1.19 + The name of the tool you want to test.
1.20 + Currently supported: gcc or g++
1.21 + Default: gcc
1.22 +
1.23 DG_TARGET_HOSTNAME
1.24 + The hostname or IP of the machine to execute run-tests
1.25 + Default: 127.0.0.1
1.26 +
1.27 DG_TARGET_USERNAME
1.28 + Execute the run-test as this user on DG_TARGET_HOSTNAME
1.29 + Default: root
1.30 +
1.31 DG_C_TESTS
1.32 DG_CPP_TESTS
1.33 -DG_TOOLCHAIN_DIR
1.34 -DG_SRC_DIR
1.35 + The C/C++ tests you want to check
1.36 + Default: (empty, means all tests)
1.37
1.38
1.39 Run examples
1.40 @@ -53,19 +59,25 @@
1.41
1.42 On host do:
1.43 ssh-keygen -t rsa (then simply press enter thru all steps)
1.44 -scp ~/.ssh/id_rsa.pub <username>@<target IP>:~/
1.45 -
1.46 -On target do:
1.47 -cd ~
1.48 -mkdir .ssh
1.49 -cat id_rsa.pub >> .ssh/authorized_keys
1.50 -rm id_rsa.pub
1.51 +ssh-copy-id -i ~/.ssh/id_rsa.pub <username>@<target IP>
1.52
1.53 Now automatic ssh login should work - test by doing a simple ssh session to target.
1.54
1.55 Note: The procedure might be slightly different for your particular target.
1.56
1.57
1.58 +Getting rid of the test-suite
1.59 +-----------------------------
1.60 +
1.61 +If you no longer have a need for the test-suite, then you can remove it altogether
1.62 +from your toolchain. Just delete the test-suite/ dub-dir.
1.63 +
1.64 +
1.65 Author
1.66 ------
1.67 Martin Lund <mgl@doredevelopment.dk>
1.68 + Initial content
1.69 +
1.70 +"Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
1.71 + Getting rid of the test-suite
1.72 + Minor fixes