GDB 4.18 on SVR5: missed it by a hair

[Robert Lipe]

Rats.

The round of optimizations we performed on configure.host didn't
make it to configure.tgt.   So SVR5 gets detected as SVR4.0 so it
gets /proc filesystem handling silently wrong. :-(

$ diff -u configure.tgt_ configure.tgt
--- configure.tgt_      Wed Apr  7 16:00:17 1999
+++ configure.tgt       Wed Apr 14 16:51:56 1999
@@ -98,9 +98,9 @@
                configdirs="${configdirs} gdbserver" ;;
 i[3456]86-*-solaris*)  gdb_target=i386sol2 ;;
 i[3456]86-*-sunos*)    gdb_target=sun386 ;;
-i[3456]86-*-sysv4.2MP) gdb_target=i386v42mp ;;
-i[3456]86-*-sysv4.2uw2*)       gdb_target=i386v42mp ;;
+i[3456]86-*-sysv4.2*)  gdb_target=i386v42mp ;;
 i[3456]86-*-sysv4*)    gdb_target=i386v4 ;;
+i[3456]86-*-sysv5*)    gdb_target=i386v42mp ;;
-i[3456]86-*-unixware2*)        gdb_target=i386v42mp ;;
+i[3456]86-*-unixware*)        gdb_target=i386v42mp ;;
-i[3456]86-*-unixware*) gdb_target=i386v4 ;;
 i[3456]86-*-sco3.2v4*) gdb_target=i386sco4 ;;

I posit that all Unixwares were SVR4.2 based and there were no 4.2's
that weren't also 4.2MP.   

Anybody that is still running the (never officially released and
probably 6 or 7 years old) SVR4.1/ES or SVR4.1/MP products on x86s
deserves anguish anyway...

If you aren't brave enough to optimize the redundant UW and 4.2*
combinations away, at least pleast add the line that treats sysv5* 
as i386v42mp.

Thanx,
RJL