From: Kevin Buettner <kevinb@redhat.com>
To: gdb@sources.redhat.com
Subject: Re: Status on cross builds
Date: Mon, 07 Nov 2005 19:43:00 -0000 [thread overview]
Message-ID: <20051107124254.53be3783@ironwood.lan> (raw)
In-Reply-To: <20051102181756.GB979@adacore.com>
On Wed, 2 Nov 2005 10:17:56 -0800
Joel Brobecker <brobecker@adacore.com> wrote:
> Just as a sanity check before creating the 6.4 branch, I ran the
> gdb_mbuild.sh script. Here are the results:
>
> * Build fails, but succeeds if we remove -Werror:
> arm-elf: compile failed
> avr: compile failed
> frv-elf: compile failed
> h8300-elf: compile failed
> ia64-linux-gnu: compile failed
> m32r-elf: compile failed
> m68hc11-elf: compile failed
> mips-elf: compile failed
> sh-elf: compile failed
> v850-elf: compile failed
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?
> * Build fails, even without -Werror:
> ms1-elf: compile failed
> configure: error: "*** Gdb does not support target ms1-unknown-elf"
This is very strange. I just did a clean checkout and managed to build
ms1-elf _with_ -Werror. (I did the build on a Fedora Core 3 machine if that
matters.)
next prev parent reply other threads:[~2005-11-07 19:43 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 [this message]
2005-11-07 22:24 ` Joel Brobecker
2005-11-07 22:38 ` Joel Brobecker
2005-11-08 1:56 ` Kevin Buettner
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=20051107124254.53be3783@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).