From: Stan Shebs <shebs@apple.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: cagney@gnu.org, gdb-patches@sources.redhat.com
Subject: Re: [commit] note non-building architectures
Date: Mon, 02 May 2005 16:50:00 -0000 [thread overview]
Message-ID: <42765A10.5050603@apple.com> (raw)
In-Reply-To: <200505021635.j42GZHeH011543@elgar.sibelius.xs4all.nl>
Mark Kettenis wrote:
> Date: Mon, 02 May 2005 11:57:10 -0400
> From: Andrew Cagney <cagney@gnu.org>
>
> Mark Kettenis wrote:
> > Date: Sun, 01 May 2005 19:11:47 -0400
> > From: Andrew Cagney <cagney@gnu.org>
> >
> > As part of getting ready for GCC 4, I've found that a number of arches
> > don't build with gcc-3.4 when using gdb_mbuild.sh. As an aid, and to
> > stop me and presumably others from going round in circles, I've updated
> > the MAINTAINERS file to both reflect current reality note the problem.
> >
> > I think your GCC 3.4 is busted.
>
> My GCC? What a strange turn of expression. I'm pretty sure the warning
> will also happen with your gcc.
>
>Nope, 2.95.3 and 3.3.5 are fine. And as Andreas Schwab there's a GCC
>bug report for this problem. Alas, this is not an ideal world where
>compiler warnings involve no false positives.
>
>This will probably be fixed eventually, either on the GCC side, or by
>adding a workaround to BFD. Meanwhile I want us to take notice that
>the fact that vax and m68k are in pretty good shape and that listing
>them as broken in MAINTAINERS is no indication that there is something
>wrong with those targets themselves.
>
Perhaps the status note could be enhanced to say
"builds with -Wno-error" or some such.
Stan
next prev parent reply other threads:[~2005-05-02 16:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-01 23:14 Andrew Cagney
2005-05-01 23:32 ` Mark Kettenis
2005-05-01 23:54 ` Andreas Schwab
2005-05-02 15:58 ` Andrew Cagney
2005-05-02 16:35 ` Mark Kettenis
2005-05-02 16:50 ` Stan Shebs [this message]
2005-05-10 3:47 ` Hans-Peter Nilsson
2005-05-19 16:53 ` Andrew Cagney
2005-05-19 19:31 ` Hans-Peter Nilsson
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=42765A10.5050603@apple.com \
--to=shebs@apple.com \
--cc=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=mark.kettenis@xs4all.nl \
/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