Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <kettenis@gnu.org>
To: cagney@gnu.org
Cc: drow@false.org, joseph@codesourcery.com, kevinb@redhat.com,
	gdb-patches@sources.redhat.com
Subject: Re: Assume solib.h
Date: Tue, 16 Nov 2004 19:45:00 -0000	[thread overview]
Message-ID: <200411161944.iAGJiI3s000752@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <419A2B43.6050805@gnu.org> (message from Andrew Cagney on Tue, 16 Nov 2004 11:30:59 -0500)

   Date: Tue, 16 Nov 2004 11:30:59 -0500
   From: Andrew Cagney <cagney@gnu.org>

   It could by now have even been committed, if only we'd not been dragged 
   down this rat-hole where people start insisting that it has to be tested 
   on old crufty systems that likely don't even build.  If you want drive 
   away native GNU and GNU/Linux developers from what is ment to be a GNU 
   project, tell them to fix vax-ultrix.

To set this straight: vax-ultrix is an old crufty system that *does*
build.  But can we please leave vax-ultrix out of this discussion.  As
soon as it really hampers progress, I'll happily scrap it.

While I recognize that GDB's primary target is GNU/Linux, moving into
the direction of GDB as a GNU-only debugger is a bad idea.  As I've
stated before, support for other systems makes us take the right
design issues.  But what's more important, by turning GDB into a
GNU-only debugger you'll probably loose some of the few active
contributors that we have left.

Mark


  reply	other threads:[~2004-11-16 19:45 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-11 19:39 Andrew Cagney
2004-11-11 20:06 ` Mark Kettenis
2004-11-11 21:48   ` Andrew Cagney
2004-11-11 22:24     ` Mark Kettenis
2004-11-12 15:52       ` Andrew Cagney
2004-11-12 17:20         ` Eli Zaretskii
2004-11-15 21:32           ` Kevin Buettner
2004-11-15 23:35             ` Mark Kettenis
2004-11-17 17:35             ` Eli Zaretskii
2004-11-15 23:59           ` Andrew Cagney
2004-11-16  1:20             ` Daniel Jacobowitz
2004-11-16  5:00             ` Eli Zaretskii
2004-11-16  8:37               ` Mark Kettenis
2004-11-16 20:54                 ` Eli Zaretskii
2004-11-16 16:14               ` Andrew Cagney
2004-11-16 19:18                 ` Mark Kettenis
2004-11-18 14:10                   ` Andrew Cagney
2004-11-18 14:37                     ` Mark Kettenis
2004-11-18 17:28                       ` Kevin Buettner
2004-11-19 17:11                       ` Andrew Cagney
2004-11-19 17:25                         ` Randolph Chung
2004-11-19 17:36                           ` Joel Brobecker
2004-11-19 17:40                             ` Randolph Chung
2004-11-19 17:56                               ` Joel Brobecker
2004-11-19 19:29                         ` Joseph S. Myers
2004-11-16 21:06                 ` Eli Zaretskii
2004-11-16 22:27                   ` Andrew Cagney
2004-11-17  4:52                     ` Eli Zaretskii
2004-11-16  1:40         ` Daniel Jacobowitz
2004-11-16  4:54           ` Eli Zaretskii
2004-11-16 16:31           ` Andrew Cagney
2004-11-16 19:45             ` Mark Kettenis [this message]
2004-11-16 21:06             ` Eli Zaretskii
2004-11-12  1:11 ` Randolph Chung
2004-11-13  1: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=200411161944.iAGJiI3s000752@elgar.sibelius.xs4all.nl \
    --to=kettenis@gnu.org \
    --cc=cagney@gnu.org \
    --cc=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=joseph@codesourcery.com \
    --cc=kevinb@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