Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: LeakyStain <leakstan@erols.com>
Cc: gdb@sources.redhat.com
Subject: Re: Obsolete m32r?
Date: Thu, 10 Jan 2002 14:28:00 -0000	[thread overview]
Message-ID: <3C3E1592.633CD862@erols.com> (raw)
In-Reply-To: <3C3C7CC8.4070409@cygnus.com>

It would help if the gdbint.info was updated first, to label the macros
obsolete or deprecated, and describe multi-arch more completely.

I started working on a port of gdb 5.0 to the ut69r in September 2001, 
and I read gdbint.info pretty thoroughly; there was only one mention of
multi-arch, and it was pretty obscure. So I implemented the macros, and 
now I discover I have to change them.

-- Stephe

Andrew Cagney wrote:

> In GDB 5.2 we're ment to have everything multi-arched so this target
> needs to be done.   I don't actually think that goal will be achived but
> we should at least be working on it.
> 
> Andrew


  reply	other threads:[~2002-01-10 22:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-06  9:44 Andrew Cagney
2002-01-06 21:23 ` Michael Snyder
2002-01-09  9:24   ` Andrew Cagney
2002-01-10 14:28     ` LeakyStain [this message]
2002-01-10 15:51       ` gdbint.info; Was: " Andrew Cagney
2002-01-16 16:25 Doug Evans
2002-01-16 16:37 ` Michael Snyder

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=3C3E1592.633CD862@erols.com \
    --to=leakstan@erols.com \
    --cc=gdb@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