From: Robert Lipe <robertl@sco.com>
To: gdb-patches@cygnus.com
Subject: GDB 4.18 on SVR5: missed it by a hair
Date: Thu, 15 Apr 1999 20:55:00 -0000 [thread overview]
Message-ID: <19990415225503.A10488@rjlhome.sco.com> (raw)
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
next reply other threads:[~1999-04-15 20:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-15 20:55 Robert Lipe [this message]
1999-04-19 13:47 ` Stan Shebs
[not found] ` <199904192047.NAA18881.cygnus.patches.gdb@andros.cygnus.com>
1999-04-19 18:13 ` Andrew Cagney
1999-04-19 19:10 ` Andrew Cagney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19990415225503.A10488@rjlhome.sco.com \
--to=robertl@sco.com \
--cc=gdb-patches@cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox