public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: gdb@sources.redhat.com
Subject: Re: Status on cross builds
Date: Tue, 08 Nov 2005 01:56:00 -0000	[thread overview]
Message-ID: <20051107185559.68a8d841@ironwood.lan> (raw)
In-Reply-To: <20051107222431.GG1635@adacore.com>

On Mon, 7 Nov 2005 14:24:31 -0800
Joel Brobecker <brobecker@adacore.com> wrote:

> > I'll take a look at ia64-linux-gnu and frv-elf.  Do you want -Werror cleanups
> > applied to both the release branch and mainline or mainline only?
> 
> IMO, only mainline is fine, especially if the warnings do not point
> at a blocking bug.

I've just committed some suitable fixes to the mainline which allow
ia64-linux-gnu and frv-elf to once again build using -Werror.

The frv-elf fixes were all gdb_byte related and the ia64 fix was a
one-liner which simply changed a floatformat related type.  As such,
I don't think these need to go on the release branch, though if someone
wants them there, I'm willing to commit to the branch as well.

Kevin

      parent reply	other threads:[~2005-11-08  1:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-02 18:18 Joel Brobecker
2005-11-02 18:24 ` Daniel Jacobowitz
2005-11-02 18:58   ` Eli Zaretskii
2005-11-02 23:28   ` Mark Kettenis
2005-11-03 21:13     ` Daniel Jacobowitz
2005-11-03 22:51       ` Mark Kettenis
2005-11-03 22:52         ` Daniel Jacobowitz
2005-11-02 23:35 ` Mark Kettenis
2005-11-03 19:56   ` Stephane Carrez
2005-11-03 21:20     ` Mark Kettenis
2005-11-04 10:19   ` Corinna Vinschen
2005-11-04 10:34     ` Andreas Schwab
2005-11-07 19:43 ` Kevin Buettner
2005-11-07 22:24   ` Joel Brobecker
2005-11-07 22:38     ` Joel Brobecker
2005-11-08  1:56     ` Kevin Buettner [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=20051107185559.68a8d841@ironwood.lan \
    --to=kevinb@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).