Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <dmj+@andrew.cmu.edu>
To: Kevin Buettner <kevinb@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: PATCH: solib-svr4.c needs to know what DT_MIPS_RLD_MAP is
Date: Mon, 18 Jun 2001 19:53:00 -0000	[thread overview]
Message-ID: <20010618195330.A13195@nevyn.them.org> (raw)
In-Reply-To: <1010619002803.ZM6862@ocotillo.lan>

On Mon, Jun 18, 2001 at 05:28:03PM -0700, Kevin Buettner wrote:
> On Jun 8,  2:07pm, Daniel Jacobowitz wrote:
> 
> > A block in solib-svr4.c is #ifdef'd on DT_MIPS_RLD_MAP, which is defined in
> > "elf/mips.h".  Including that file would probably help.  We could
> > conditionally include this file based on target, but I just went by other
> > files in GDB which referenced it and included it always.
> > 
> > How's this patch?
> 
> This patch is approved.  Let me know if you need me to check it in for
> you.  (I would prefer to see your name added to the MAINTAINERS file
> so that you can check it in yourself.)

I can't check in at the moment, but I'd certainly appreciate being
added to MAINTAINERS - I'm going to be submitting an entire port in the
rapidly approaching future.  I'd appreciate it if you would check this
in; meanwhile, what should I do (besides the copyright assignment,
which is in progress) in order to gain checkin privileges?

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2001-06-18 19:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-08 14:07 Daniel Jacobowitz
2001-06-18 17:28 ` Kevin Buettner
2001-06-18 19:53   ` Daniel Jacobowitz [this message]
2001-06-19  8:40   ` Andrew Cagney
2001-06-25 17:48     ` Kevin Buettner
2001-07-02 12:38   ` Daniel Jacobowitz

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=20010618195330.A13195@nevyn.them.org \
    --to=dmj+@andrew.cmu.edu \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kevinb@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