Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@redhat.com>
To: Paolo Bonzini <paolo.bonzini@lu.unisi.ch>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
	binutils@sources.redhat.com, gdb-patches@sources.redhat.com,
	DJ Delorie <dj@delorie.com>
Subject: Re: PR/17383: fix gcc in-srcdir build (take 2)
Date: Mon, 28 Feb 2005 17:20:00 -0000	[thread overview]
Message-ID: <4222E88B.8080608@redhat.com> (raw)
In-Reply-To: <422061B2.1080507@lu.unisi.ch>

Hi Paolo,

> It has passed in-srcdir and out-of-srcdir builds of gcc (all languages,
> powerpc-apple-darwin7.8.0) and binutils+gdb (i686-pc-linux-gnu).  Ok for
> gcc/src?


Approved for binutils.

Cheers
   Nick



  reply	other threads:[~2005-02-28  9:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-27  0:27 Paolo Bonzini
2005-02-28 17:20 ` Nick Clifton [this message]
2005-03-01 15:17 ` Mike Stump
2005-03-01 23:02   ` Mark Mitchell
2005-02-27  0:36 Nathanael Nerode
2005-02-27  8:23 ` Alexandre Oliva
2005-02-27 15:46   ` DJ Delorie
2005-02-28  4:29   ` Paolo Bonzini
2005-02-28  9:35 ` Paolo Bonzini

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=4222E88B.8080608@redhat.com \
    --to=nickc@redhat.com \
    --cc=binutils@sources.redhat.com \
    --cc=dj@delorie.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=paolo.bonzini@lu.unisi.ch \
    /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