This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: autotools transition report: need a flag day
- From: Phil Edwards <phil at jaj dot com>
- To: Dan Kegel <dank at kegel dot com>
- Cc: libstdc++ at gcc dot gnu dot org
- Date: Thu, 28 Aug 2003 17:52:28 -0400
- Subject: Re: autotools transition report: need a flag day
- References: <3F4B8197.2060900@kegel.com> <3F4B8E22.5070800@kegel.com>
On Tue, Aug 26, 2003 at 09:43:14AM -0700, Dan Kegel wrote:
> cd $TARGET/$LIBSTDCXX_DIR/testsuite
> runtest --tool=$LIBSTDCXX_TEST --target=$TARGET -v || echo Some $LIBSTDCXX_TEST test failed...
Try adding "make site.exp" between those commands.
> (I'm invoking runtest directly
> rather than 'make check'. Guess I'm paying for that now, but
> invoking it directly makes it a lot easier to figure out how
> options get passed to runtest :-)
Simplifying only a tiny bit, the generated make lines are basically:
AM_RUNTESTFLAGS =
RUNTESTDEFAULTFLAGS = --tool $$tool --srcdir $$srcdir
RUNTESTFLAGS =
DEJATOOL = libstdc++
check-DEJAGNU: site.exp
srcdir=/path/to/source; \
l='$(DEJATOOL)'; for tool in $$l; do \
runtest $(AM_RUNTESTFLAGS) $(RUNTESTDEFAULTFLAGS) $(RUNTESTFLAGS); \
done; \
Once, the variables and loops come out, it's just
runtest --tool libstdc++ --srcdir /path/to/source
ith the target and everything else taken from the generated site.exp.
The way you pass additional flags is by setting RUNTESTFLAGS on the make
command line:
make check RUNTESTFLAGS="--verbose"
--
Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it.
- Brian W. Kernighan