public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Corinna Vinschen <vinschen@redhat.com>
To: gdb@sources.redhat.com
Subject: Re: Status on cross builds
Date: Fri, 04 Nov 2005 10:19:00 -0000	[thread overview]
Message-ID: <20051104101942.GY2988@calimero.vinschen.de> (raw)
In-Reply-To: <200511022334.jA2NYv39004939@elgar.sibelius.xs4all.nl>

On Nov  3 00:34, Mark Kettenis wrote:
> > Date: Wed, 2 Nov 2005 10:17:56 -0800
> > From: Joel Brobecker <brobecker@adacore.com>
> > 
> > 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
> 
> This is an interresting list.  It might be a bit biased by the version
> of GCC used by Joel, but it either means that these targets aren't
> properly maintained, or that its maintainer needs to be educated about
> -Werror.  Or perhaps we should enable -Werror by default on the main
> branch.  Anyway, we should consider these targets aa candidates for
> removal after 6.4.

I don't think so at all.  The -Werror results are just due to the usage
of gdb_byte and I don't think that qualifies for treating these targets
as broken.  It only means that nobody touched the targets after the
gdb_byte change has been introduced, but that doesn't invalidate the
targets as a whole.  This point of view is somewhat excessive, IMHO.

FWIW, I'll have a look into h8300-elf, sh-elf and v850-elf at one point,
but the change is very likely only mechanical and could have been done
by everybody who has build these targets lately.


Corinna

-- 
Corinna Vinschen
Cygwin Project Co-Leader
Red Hat, Inc.

  parent reply	other threads:[~2005-11-04 10:19 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 [this message]
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

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=20051104101942.GY2988@calimero.vinschen.de \
    --to=vinschen@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).