Re: [PATCH] quoting curly braces in call-rt-st

[Michael Elizabeth Chastain <chastain at cygnus dot com>]

Here is how I build my Dejagnu, as of this weekend's test run.

First I have baseline versions of TCL and Expect:

  ftp://tcl.activestate.com/pub/tcl/tcl8_0/tcl8.0.5.tar.gz
  http://expect.nist.gov/src/expect-5.30.tar.gz

These are not the latest versions of TCL and Expect, but they
work for me.

I configured TCL with "--enable-gcc" and "--disable-shared".
I configured Expect with "--disable-shared", "--with-tcl",
  "--with-tclconfig", and "--with-tclinclude".

These are installed on all the machines I use so I don't have to rebuild
them every week.

When I check out gdb, I also check out naked-dejagnu:

  CVSROOT=:pserver:anoncvs@anoncvs.cygnus.com:/cvs/src
  export CVSROOT
  expect -c 'spawn cvs login' -c 'expect password: ' -c 'send -- "anoncvs\r"' -c 'expect eof'
  cvs -z 9 co gdb binutils naked-dejagnu
  mv src source-src
  rm -rf CVS

I don't configure or make dejagnu.  When I run the gdb testsuite, it
looks for dejagnu/runtest in the source tree and finds it there.

(binutils is there because I'm also building gcc from cvs source).

My inclination is to leave the curly braces alone and just use the
known good test machinery for now.

In the future I would like to switch from the "naked-dejagnu" module
to some stable version of dejagnu.  And I'd like to firm up my scripts
and make them available to other people.  And I'd like to run the
gdb test script and have 0 ERRORs, 0 WARNINGs, and less than 10 FAILs.

MichaelC