Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Steve Ellcey <sje@cup.hp.com>
Cc: gdb-patches@gcc.gnu.org
Subject: Re: Patch for gdb build on hppa hp-ux
Date: Sat, 07 Apr 2007 17:20:00 -0000	[thread overview]
Message-ID: <20070407172000.GA24650@caradoc.them.org> (raw)
In-Reply-To: <200704062153.OAA16290@hpsje.cup.hp.com>

On Fri, Apr 06, 2007 at 02:53:09PM -0700, Steve Ellcey wrote:
> This patch fixes a build problem on hppa hp-ux.  This is the first of
> two patches I have that allow me to build gdb on hppa hp-ux.  The build
> has been broken (for me at least) for some time.  This is the only HP
> specific change that was needed.  Tested by building gdb on hppa hp-ux.
> 
> OK to checkin?

OK, although this file will be going away shortly - I ran out of time
before ESC, but I'm going to finish removing the files we agreed on
this month.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2007-04-07 17:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-06 21:53 Steve Ellcey
2007-04-07 17:20 ` Daniel Jacobowitz [this message]
2007-04-09  2:13 ` Daniel Jacobowitz
2007-04-09 23:25   ` Steve Ellcey
2007-04-10 12:05     ` Daniel Jacobowitz
2007-04-10 12:11       ` Daniel Jacobowitz
2007-04-10 17:32       ` Steve Ellcey
2007-04-10 17:41         ` Daniel Jacobowitz
2007-04-10 19:03       ` Eli Zaretskii
2007-04-10 20:22         ` Daniel Jacobowitz
2007-04-13 14:04           ` Daniel Jacobowitz
2007-04-13 17:07             ` [patch] "single step" atomic instruction sequences as a whole on PPC Luis Machado
2007-04-28 23:34               ` [RFC] " Luis Machado
2007-04-28 23:45                 ` Ulrich Weigand
2007-04-29  1:53                   ` Luis Machado

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=20070407172000.GA24650@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@gcc.gnu.org \
    --cc=sje@cup.hp.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