diff options
| author | Martin Lund <mgl@doredevelopment.dk> | 2010-05-19 17:53:04 +0200 |
|---|---|---|
| committer | Martin Lund <mgl@doredevelopment.dk> | 2010-05-19 17:53:04 +0200 |
| commit | 1779c82ad2916f9a3c3ad2dd350dbeb2d6692f9d (patch) | |
| tree | ced95e1ac1b87ffeaffa3aafa985be5e27ca621e /contrib/gcc-test-suite/README | |
| parent | 0a63e8222c2865406f0c8967fedd8a89c2c816d8 (diff) | |
| download | crosstool-ng-1779c82ad2916f9a3c3ad2dd350dbeb2d6692f9d.tar.gz crosstool-ng-1779c82ad2916f9a3c3ad2dd350dbeb2d6692f9d.tar.bz2 crosstool-ng-1779c82ad2916f9a3c3ad2dd350dbeb2d6692f9d.zip | |
test-suite: Added new test suite feature (experimental)
This patch adds support for installing the gcc test suite. A helper
Makefile is provided for building and running the gcc tests.
The default configuration runs all gcc tests and requires automatic
ssh/scp login access to a networked target board. See README for
more details.
Note: Current feature is tested with the powerpc-unknown-linux-gnu
sample but it should work with others as well.
Signed-off-by: Martin Lund <mgl@doredevelopment.dk>
Diffstat (limited to 'contrib/gcc-test-suite/README')
| -rw-r--r-- | contrib/gcc-test-suite/README | 71 |
1 files changed, 71 insertions, 0 deletions
diff --git a/contrib/gcc-test-suite/README b/contrib/gcc-test-suite/README new file mode 100644 index 00000000..99d61cce --- /dev/null +++ b/contrib/gcc-test-suite/README @@ -0,0 +1,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> |