Problems running testsuite

Problems running testsuite

[Andreas Jaeger]

I tried today to run CVS head on x86_64-linux-gnu and it failed running
the testsuite with:
Running /cvs/src-gdb/src/gdb/testsuite/gdb.gdbtk/browser.exp ...
gdb compile failed, /usr/lib64/gcc-lib/x86_64-suse-linux/3.3/../../../../x86_64-suse-linux/bin/ld: cannot open output file /usr/src/aj/build/gdb/gdb/testsuite/gdb.gdbtk/stack: No such file or directory
collect2: ld returned 1 exit status
WARNING: Testcase compile failed, so some tests in this file will automatically fail.

ERROR: /usr/src/aj/build/gdb/gdb/testsuite/../../gdb/insight does not exist.
make[2]: *** [just-check] Error 1

I configured with:
/cvs/src-gdb/src/configure  --prefix=/usr --disable-tui --disable-gdbtk --disable-nls

Since I disabled gdbtk, why is the testsuite run for it at all?  This
worked last time (a week or two ago) without problems...
The problem seems to be that gdb.gdbtk is not created in the testsuite directory.

Any ideas?

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

Re: Problems running testsuite

[Michael Elizabeth Chastain]

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

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.

Michael C

Re: Problems running testsuite

[Andreas Jaeger]

[-- 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 --]