patch for gdb 4.17.86 on OpenServer
Robert Lipe
robertl@sco.com
Thu Apr 1 00:00:00 GMT 1999
With this installed, simple breakpoints work. It clocks in at "only"
278 failures (down from 4200-ish) that, at a glance, seem to be similar
in size and shape to the failures on GNU Linux/x86 and UW7 on x86.
--- configure.tgt_ Tue Mar 23 23:34:50 1999
+++ configure.tgt Tue Mar 23 23:38:02 1999
@@ -103,6 +103,7 @@
i[3456]86-*-sysv4*) gdb_target=i386v4 ;;
i[3456]86-*-unixware2*) gdb_target=i386v42mp ;;
i[3456]86-*-unixware*) gdb_target=i386v4 ;;
+i[3456]86-*-sco3.2v5*) gdb_target=i386sco5 ;;
i[3456]86-*-sco*) gdb_target=i386v ;;
i[3456]86-*-sysv*) gdb_target=i386v ;;
i[3456]86-*-linux*) gdb_target=linux
Could someone with CVS access to the tree please walk back in time on
gdb/configure.host and gdb/configure.tgt and see if other targets may
have been deleted? I can spot at least one other target by inspection
that is missing.
OK, I won't be a tease. It's i386sco4 which should probably match
on a line something like:
i[3456]86-*-sco3.2v4*) gdb_target=i386sco4 ;;
Also, I think I recall the default (ancient) targets matching:
i[3456]86-*-sco*) gdb_target=i386sco ;;
In all, I suspect an evaluation of the CVS logs for configure.host
and configure.target might be a good idea. ChangeLogs didn't show
anything obvious.
More information about the Gdb
mailing list