author | Martin Lund <mgl@doredevelopment.dk> |
Wed May 19 17:53:04 2010 +0200 (2010-05-19) | |
changeset 1965 | e3d532dd8b5d |
child 1966 | 10ad7f230f4b |
permissions | -rw-r--r-- |
mgl@1965 | 1 |
|
mgl@1965 | 2 |
Helper Makefile for testing gcc toolchains using the gcc-testsuite |
mgl@1965 | 3 |
================================================================== |
mgl@1965 | 4 |
|
mgl@1965 | 5 |
Requirements |
mgl@1965 | 6 |
------------ |
mgl@1965 | 7 |
|
mgl@1965 | 8 |
* DejaGnu 'runtest' v1.4.4+ |
mgl@1965 | 9 |
* Make v3.81+ |
mgl@1965 | 10 |
* wget |
mgl@1965 | 11 |
|
mgl@1965 | 12 |
|
mgl@1965 | 13 |
Configuration |
mgl@1965 | 14 |
------------- |
mgl@1965 | 15 |
|
mgl@1965 | 16 |
Edit default.cfg to reflect your toolchain and target configuration. |
mgl@1965 | 17 |
|
mgl@1965 | 18 |
Alternatively, override configuration variables on the command line. |
mgl@1965 | 19 |
|
mgl@1965 | 20 |
Available config variables: |
mgl@1965 | 21 |
|
mgl@1965 | 22 |
DG_GCC_VERSION |
mgl@1965 | 23 |
DG_GCC_URL |
mgl@1965 | 24 |
DG_TOOLNAME |
mgl@1965 | 25 |
DG_TARGET |
mgl@1965 | 26 |
DG_TARGET_HOSTNAME |
mgl@1965 | 27 |
DG_TARGET_USERNAME |
mgl@1965 | 28 |
DG_C_TESTS |
mgl@1965 | 29 |
DG_CPP_TESTS |
mgl@1965 | 30 |
DG_TOOLCHAIN_DIR |
mgl@1965 | 31 |
DG_SRC_DIR |
mgl@1965 | 32 |
|
mgl@1965 | 33 |
|
mgl@1965 | 34 |
Run examples |
mgl@1965 | 35 |
------------ |
mgl@1965 | 36 |
|
mgl@1965 | 37 |
The first two examples require a networked target with ssh access and automatic |
mgl@1965 | 38 |
ssh login (see section below). Target SW should be compiled with the toolchain |
mgl@1965 | 39 |
to be tested. |
mgl@1965 | 40 |
|
mgl@1965 | 41 |
Run default gcc compile/execution tests: |
mgl@1965 | 42 |
$ make DG_TOOLNAME=gcc DG_TARGET_HOSTNAME=192.168.17.93 DG_TARGET_USERNAME=root |
mgl@1965 | 43 |
|
mgl@1965 | 44 |
Run default g++ compile/execution tests: |
mgl@1965 | 45 |
$ make DG_TOOLNAME=g++ DG_TARGET_HOSTNAME=192.168.17.93 DG_TARGET_USERNAME=root |
mgl@1965 | 46 |
|
mgl@1965 | 47 |
Run selected gcc compile only tests (no target required): |
mgl@1965 | 48 |
$ make DG_TOOLNAME=gcc DG_C_TESTS="compile.exp noncompile.exp" |
mgl@1965 | 49 |
|
mgl@1965 | 50 |
|
mgl@1965 | 51 |
SSH automatic login configuration example |
mgl@1965 | 52 |
----------------------------------------- |
mgl@1965 | 53 |
|
mgl@1965 | 54 |
On host do: |
mgl@1965 | 55 |
ssh-keygen -t rsa (then simply press enter thru all steps) |
mgl@1965 | 56 |
scp ~/.ssh/id_rsa.pub <username>@<target IP>:~/ |
mgl@1965 | 57 |
|
mgl@1965 | 58 |
On target do: |
mgl@1965 | 59 |
cd ~ |
mgl@1965 | 60 |
mkdir .ssh |
mgl@1965 | 61 |
cat id_rsa.pub >> .ssh/authorized_keys |
mgl@1965 | 62 |
rm id_rsa.pub |
mgl@1965 | 63 |
|
mgl@1965 | 64 |
Now automatic ssh login should work - test by doing a simple ssh session to target. |
mgl@1965 | 65 |
|
mgl@1965 | 66 |
Note: The procedure might be slightly different for your particular target. |
mgl@1965 | 67 |
|
mgl@1965 | 68 |
|
mgl@1965 | 69 |
Author |
mgl@1965 | 70 |
------ |
mgl@1965 | 71 |
Martin Lund <mgl@doredevelopment.dk> |