[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

whew. remote testing working. Writeup online.

From: Doug Evans
Subject: whew. remote testing working. Writeup online.
Date: Tue, 10 Jun 2003 21:47:39 -0700 (PDT)

Dan Kegel writes:
 > is my try at
 > describing how to get remote testing with dejagnu working.
 > I feel much better now.

Some notes people may or may not find useful.

1) Regarding tracing of what dejagnu is doing: try
make check RUNTESTFLAGS="-v -v -v -v"

or just "runtest -v -v -v -v ..."

Level 4 is (or has been) the max.  Try various levels.
The lower levels (-v and -v -v) are excessively verbose for my
tastes but way back when I was unable to convince the powers that be of this.

2) To avoid confusion I would replace
"The TCL command target_compile ..." and
"The TCL command remote_load ..."


"The Dejagnu function target_compile ..." and
"The Dejagnu function remote_load ..."

3) It'd be useful to mention the $DEJAGNU variable (or ~/.dejagnurc I think).
And while the topic of your document is remote testing the context
is cross toolchains, thus it would be nice to mention simulation.
The following also applies to target boards though, the tricky part is
setting target_list correctly plus corresponding board configuration
which you've already covered to some extent.

Suppose you've built an arm-elf toolchain (*1) and want to test it.
Here are the steps one can use:

a) Create a file, called, say ~/etc/dejagnu.exp.

In the file put:

switch -glob "$target_triplet" {
    "arm-*-elf" {
        set target_list { arm-sim }

    default {
        send_user "ERROR: dejagnu.exp Unknown target $target_triplet\n"
        exit 1

This will create a file that tells dejagnu to use the simulator
for tool testing.

b) point $DEJAGNU at the file

bash$ export DEJAGNU=$HOME/etc/dejagnu.exp

This will save having to specify --target_board each time.

c) Then, running dejagnu reduces to:

cd $HOME/arm/b-binutils
make -k check
cd $HOME/arm/b-gcc
make -k check
cd $HOME/arm/b-gdb
make -k check

(*1) For completeness' sake, having just built it, here's what I did:

cd $HOME/arm
mkdir rel
tar xfz binutils-
tar xfz gcc-3.3.tar.gz
tar xfz newlib-1.11.0.tar.gz
tar xfz gdb-5.3.tar.gz
mkdir b-binutils b-gcc b-newlib b-gdb
cd b-binutils
../binutils- --target=arm-elf --prefix=$HOME/arm/rel
make install
cd ../b-gcc
../gcc-3.3/configure --target=arm-elf --prefix=$HOME/arm/rel 
make install
cd ../b-newlib
../newlib-1.11.0/configure --target=arm-elf --prefix=$HOME/arm/rel
make install
cd ../b-gdb
../gdb-5.3/configure --target=arm-elf --prefix=$HOME/arm/rel
make install

reply via email to

[Prev in Thread] Current Thread [Next in Thread]