Re: Problems running testsuite

[Andreas Jaeger <aj@suse.de>]

[-- Attachment #1: Type: text/plain, Size: 1350 bytes --]

Michael Elizabeth Chastain <mec@shout.net> writes:

> Did you a "cvs update -d" to get the new
> gdb/testsuite/gdb.cp directory?

No, I'm using:
cvs -d :pserver:anoncvs@music:/cvs/src co -N -d src-gdb gdb

> If you did, I bet that you got gdb/testsuite/gdb.gdbtk at the
> same time.
>
> Try just removing gdb/testsuite/gdb.gdbtk by hand.
>
> The gdb module includes:
>
>   naked-gdb       -a !src/gdb/gdbtk !src/gdb/testsuite/gdb.gdbtk src/gdb
>
> So usually you don't get gdb.gdbtk.  But "cvs update -d"
> doesn't pay attention to modules, so gdb.gdbtk comes in.

I'll did a fresh-check out again and still get gdb.gdbtk.  Seems to be
a bug in CVS :-(

But nevertheless I have this for some weeks already and only recently
it failed.

What puzzles me is that configure check for --enable-gdbtk and does:
if test $enable_gdbtk = yes; then
  configdirs="$configdirs gdb.gdbtk"
fi

I updated my system and that might be the reason, I see the same
failure with gdb-6 now.

Ok, I'll rm -rf gdb.gdbtk now.  

Or do you see a better way to test gdb without an X display available
except using --disable-gdbtk?

Andreas
-- 
 Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj
  SuSE Linux AG, Deutschherrnstr. 15-19, 90429 Nürnberg, Germany
   GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]