From: Zack Weinberg <zack@codesourcery.com>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: gcc@gcc.gnu.org, gbsadler1@lcisp.com
Subject: Re: 3.1 branch ada bootstrap fails
Date: Mon, 06 May 2002 13:28:00 -0000 [thread overview]
Message-ID: <20020506202810.GJ2542@codesourcery.com> (raw)
In-Reply-To: <200205061512.g46FCZVa027683@hiauly1.hia.nrc.ca>
On Mon, May 06, 2002 at 11:12:35AM -0400, John David Anglin wrote:
> > I am not sure whether ALL_CFLAGS wouldn't have other junk, such as
> > unwanted -D switches. However, if it doesn't, it is likely to be
> > safer to do that.
> >
> > Can you work up a patch? I've got too many things to juggle right
> > now, and this is apparently a release concern.
>
> For the moment, I decided that it would be better not to propose
> another solution. Mark has been presented with a couple of alternatives:
>
> 1) Documentation change (ADAC should be same as CC).
> 2) Port from trunk Geoffrey Keating's configure patch to check if
> -Wno-long-long is supported by the ada driver.
I'm in favor of (2), for what it's worth; we know it works on the
trunk.
zw
next prev parent reply other threads:[~2002-05-06 20:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-03 10:09 John David Anglin
2002-05-03 10:32 ` Zack Weinberg
2002-05-03 11:03 ` John David Anglin
2002-05-05 16:06 ` Zack Weinberg
2002-05-06 8:38 ` John David Anglin
2002-05-06 13:28 ` Zack Weinberg [this message]
2002-05-06 15:17 ` Mark Mitchell
2002-05-06 15:26 ` John David Anglin
2002-05-06 15:31 ` Mark Mitchell
2002-05-07 11:48 ` John David Anglin
2002-05-07 17:02 ` Alexandre Oliva
2002-05-07 17:54 ` Alexandre Oliva
2002-05-07 20:06 ` Mark Mitchell
2002-05-07 18:02 ` Alexandre Oliva
2002-05-07 18:05 ` John David Anglin
2002-05-03 11:39 ` Alexandre Oliva
2002-05-03 12:58 ` John David Anglin
2002-05-03 19:47 ` Geoff Keating
2002-05-03 21:33 ` Alexandre Oliva
-- strict thread matches above, loose matches on Subject: below --
2002-05-04 23:52 Simon Wright
2002-05-03 8:32 Gordon Sadler
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=20020506202810.GJ2542@codesourcery.com \
--to=zack@codesourcery.com \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=gbsadler1@lcisp.com \
--cc=gcc@gcc.gnu.org \
/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).