Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <kettenis@gnu.org>
To: eliz@gnu.org
Cc: cagney@gnu.org, gdb-patches@sources.redhat.com
Subject: Re: [RFC] Suggested ways to remove the need for xm-go32.h
Date: Sun, 26 Sep 2004 18:38:00 -0000	[thread overview]
Message-ID: <200409261837.i8QIbuxo001262@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <01c4a31e$Blat.v2.2.2$91a0d700@zahav.net.il> (eliz@gnu.org)

   Date: Sat, 25 Sep 2004 18:40:53 +0200
   From: "Eli Zaretskii" <eliz@gnu.org>

   > Date: Fri, 24 Sep 2004 11:03:08 -0400
   > From: Andrew Cagney <cagney@gnu.org>
   > Cc: Michael Chastain <mec.gnu@mindspring.com>, me@cgf.cx,
   >         gdb-patches@sources.redhat.com
   > 
   > We've no evidence that we've a real problem here, and hence no evidence 
   > that a wrapper is needed.  All I see a dig achieving is to flush out 
   > legacy systems on which GDB no longer builds.  If someone with such a 
   > legacy system really really needs a modern GDB then I'm sure that 
   > they'll step up to the challenge of solving this and many other problem.

   Mark, how do you feel about losing the wrappers?  Would it be okay for
   me to do it that way, or do you feel strongly about them?

I don't feel too strongly about it.  The "b" modifier is mentioned in
the 4.3BSD/Net2 headers, and Ultrix 4.0 also has it.  That's pretty
ancient stuff.  But I'd appreciate it if you, and other people, keep
in the back of your mind that there may still be systems that don't
support the "b" modifier.  So avoid using "b" wherever possible, and
keep using the macro's from include/fopen-*.h.

In the discussion we've had over the past days people have been taling
about supported and unsupported hosts, as if there is some restricted
list of machines that GDB runs on.  While that's currently the case, I
think it's wrong to think about it like that.  Yes, we have a list of
supported *native* hosts, but actually it should be possible to
compile GDB on any system that's POSIX-ish.  If that system isn't on
the list of native host, you wouldn't get the ability to debug native
programs, but you'd still be able to use the remote protocol to debug
programs on another system.  Therefore we should try to make the
generic parts of GDB as portable as we can.  IMHO, compiling GDB on
ancient systems helps to keep us honest about that.  That's why I
recently added back the vax-dec-ultrix4* stuff.

Cheers,

Mark


  reply	other threads:[~2004-09-26 18:38 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-18 13:21 Eli Zaretskii
2004-09-19 11:44 ` Mark Kettenis
2004-09-20  3:33   ` Eli Zaretskii
2004-09-22 20:21     ` Michael Chastain
2004-09-23  4:51       ` Eli Zaretskii
2004-09-23  6:02         ` Michael Chastain
2004-09-23  8:14   ` Corinna Vinschen
2004-09-23  5:03 ` Christopher Faylor
2004-09-23  6:30   ` Michael Chastain
2004-09-23  8:02     ` Corinna Vinschen
2004-09-24 10:51       ` Eli Zaretskii
2004-09-24 14:35         ` Andrew Cagney
2004-09-23 13:56     ` Christopher Faylor
2004-09-23 17:20       ` Michael Chastain
2004-09-23 17:24         ` Christopher Faylor
2004-09-23 15:18     ` Joel Brobecker
2004-09-23 17:57       ` Daniel Jacobowitz
2004-09-24 15:05         ` Andrew Cagney
2004-09-25 16:43           ` Eli Zaretskii
2004-09-26 18:38             ` Mark Kettenis [this message]
2004-09-27  2:29           ` Daniel Jacobowitz
2004-09-23 20:58   ` Mark Kettenis
2004-09-23 21:14     ` Christopher Faylor
2004-09-24 10:48       ` Eli Zaretskii
2004-09-24 12:23         ` Corinna Vinschen
2004-09-24 13:39           ` Andreas Schwab
2004-09-24 19:51             ` Christopher Faylor
2004-09-24 21:16               ` Christopher Faylor
2004-09-24 21:32               ` Andreas Schwab
2004-09-24 13:40           ` Eli Zaretskii
2004-09-24 16:49           ` Ian Lance Taylor

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=200409261837.i8QIbuxo001262@elgar.sibelius.xs4all.nl \
    --to=kettenis@gnu.org \
    --cc=cagney@gnu.org \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sources.redhat.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