Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@ges.redhat.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa/i386] Consolidate i386 targets
Date: Mon, 05 Aug 2002 10:04:00 -0000	[thread overview]
Message-ID: <3D4EB016.2050607@ges.redhat.com> (raw)
In-Reply-To: <Pine.SUN.3.91.1020805073757.25320A-100000@is>

> On Sun, 4 Aug 2002, Andrew Cagney wrote:
> 
> 
>> Yes, DJGPP is definitly still supported.  DJGPP is a native 
>> configuration though, and the above list applies to the cross debuggers.
> 
> 
> I think that might confuse someone (it did confuse me): there's only one 
> list of targets in MAINTAINERS, so I thought it pertains to any valid 
> target supported by GDB, whether native or cross.

Something to clarify, yes.  That list is just the target architectures 
-- i386, sh, ia64, et.al.

DJGPP while depending on the i386 architecture is a native so is listed 
under Host/Native.

>  If you remove DJGPP 
> from that list, it might cause someone to think DJGPP is no longer 
> supported.

Sounds like I should re-structure the file.  As an aside, RMS has noted 
that we should be using the correct GNU/Linux tuple name.

Hmm, given there are other redundant targets (rs6000) and targets with 
unfortunate names (s390-linux), I should overhaul the section.  The 
DJGPP change will then make more sense.

> Note that I don't have anything against the change to config.tgt.

I'll split that out.

Andrew



      reply	other threads:[~2002-08-05 17:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-03 13:36 Andrew Cagney
2002-08-03 22:31 ` Eli Zaretskii
2002-08-04 10:44   ` Andrew Cagney
2002-08-04 21:46     ` Eli Zaretskii
2002-08-05 10:04       ` Andrew Cagney [this message]

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=3D4EB016.2050607@ges.redhat.com \
    --to=ac131313@ges.redhat.com \
    --cc=eliz@is.elta.co.il \
    --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