summaryrefslogtreecommitdiff
path: root/contrib/gcc-test-suite/README
blob: 99d61ccea52da63d9d597d0447d743b3ce20fbb3 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
Helper Makefile for testing gcc toolchains using the gcc-testsuite
==================================================================

Requirements
------------

* DejaGnu 'runtest' v1.4.4+
* Make v3.81+
* wget


Configuration
-------------

Edit default.cfg to reflect your toolchain and target configuration.

Alternatively, override configuration variables on the command line.

Available config variables:

DG_GCC_VERSION
DG_GCC_URL
DG_TOOLNAME
DG_TARGET
DG_TARGET_HOSTNAME
DG_TARGET_USERNAME
DG_C_TESTS
DG_CPP_TESTS
DG_TOOLCHAIN_DIR
DG_SRC_DIR


Run examples
------------

The first two examples require a networked target with ssh access and automatic
ssh login (see section below). Target SW should be compiled with the toolchain 
to be tested.

Run default gcc compile/execution tests:
$ make DG_TOOLNAME=gcc DG_TARGET_HOSTNAME=192.168.17.93 DG_TARGET_USERNAME=root

Run default g++ compile/execution tests:
$ make DG_TOOLNAME=g++ DG_TARGET_HOSTNAME=192.168.17.93 DG_TARGET_USERNAME=root

Run selected gcc compile only tests (no target required):
$ make DG_TOOLNAME=gcc DG_C_TESTS="compile.exp noncompile.exp" 


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

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.


Author
------
Martin Lund <mgl@doredevelopment.dk>