public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "zack@codesourcery.com" <zack@codesourcery.com>
To: danglin@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: ada/6483: ada fails to build under hppa*-hp-hpux*
Date: Tue, 30 Apr 2002 14:56:00 -0000 [thread overview]
Message-ID: <20020430215600.11313.qmail@sources.redhat.com> (raw)
The following reply was made to PR ada/6483; it has been noted by GNATS.
From: "zack@codesourcery.com" <zack@codesourcery.com>
To: Mark Mitchell <mark@codesourcery.com>
Cc: John David Anglin <dave@hiauly1.hia.nrc.ca>,
"fw@deneb.enyo.de" <fw@deneb.enyo.de>,
"dave.anglin@nrc.ca" <dave.anglin@nrc.ca>,
"gcc-gnats@gcc.gnu.org" <gcc-gnats@gcc.gnu.org>
Subject: Re: ada/6483: ada fails to build under hppa*-hp-hpux*
Date: Tue, 30 Apr 2002 14:46:57 -0700
On Tue, Apr 30, 2002 at 11:15:14AM -0700, Mark Mitchell wrote:
>
> >As far as I understand the situation, it only needs to be applied
> >to the c and ada files in the ada subdirectory. We don't need
> >to build all of gcc with -mdisable-indexing.
>
> Thanks to both of you for explaining this situation.
>
> >This is what I suggested
> ><http://gcc.gnu.org/ml/gcc-patches/2002-04/msg01625.html>.
>
> OK. Check that version in, and let's close the PR.
I'd suggest renaming ADA_CFLAGS to X_ADA_CFLAGS so it is clear that
this is for use in x-fragments. Probably only worth doing on the
mainline.
zw
next reply other threads:[~2002-04-30 21:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-30 14:56 zack [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-30 14:56 Mark Mitchell
2002-04-30 14:56 John David Anglin
2002-04-30 12:21 danglin
2002-04-30 11:26 Mark Mitchell
2002-04-30 11:16 John David Anglin
2002-04-30 11:06 zack
2002-04-30 10:46 John David Anglin
2002-04-30 10:36 John David Anglin
2002-04-30 10:26 Mark Mitchell
2002-04-30 8:36 Florian Weimer
2002-04-26 16:50 danglin
2002-04-26 16:46 dave.anglin
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=20020430215600.11313.qmail@sources.redhat.com \
--to=zack@codesourcery.com \
--cc=danglin@gcc.gnu.org \
--cc=gcc-prs@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).