public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Jeffrey Creem" <jeff@thecreems.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: ada/8689: GNAT 3.15p can not be used as 3.2.1 (others?) boostrap
Date: Sun, 18 May 2003 12:46:00 -0000 [thread overview]
Message-ID: <20030518124600.29833.qmail@sources.redhat.com> (raw)
The following reply was made to PR ada/8689; it has been noted by GNATS.
From: "Jeffrey Creem" <jeff@thecreems.com>
To: <steven@gcc.gnu.org>,
<gcc-bugs@gcc.gnu.org>,
<gcc-prs@gcc.gnu.org>,
<jeff@thecreems.com>,
<nobody@gcc.gnu.org>,
<gcc-gnats@gcc.gnu.org>
Cc:
Subject: Re: ada/8689: GNAT 3.15p can not be used as 3.2.1 (others?) boostrap
Date: Sun, 18 May 2003 08:44:13 -0400
This problem no longer appears when using the gcc-3.3 release tarballs.
Bootstrapped using gnat 3.15p on a Sparc Solaris 8 system (same system
original problem was detected on).
ada/8689 should be closed.
----- Original Message -----
From: <steven@gcc.gnu.org>
To: <gcc-bugs@gcc.gnu.org>; <gcc-prs@gcc.gnu.org>; <jeff@thecreems.com>;
<nobody@gcc.gnu.org>
Sent: Tuesday, May 13, 2003 2:34 AM
Subject: Re: ada/8689: GNAT 3.15p can not be used as 3.2.1 (others?)
boostrap
> Synopsis: GNAT 3.15p can not be used as 3.2.1 (others?) boostrap
>
> State-Changed-From-To: open->feedback
> State-Changed-By: steven
> State-Changed-When: Tue May 13 06:34:14 2003
> State-Changed-Why:
> Dara has asked for feedback
>
>
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8689
>
next reply other threads:[~2003-05-18 12:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-18 12:46 Jeffrey Creem [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-18 1:06 Jeffrey Creem
2003-05-13 6:35 steven
2003-05-13 0:06 Dara Hazeghi
2003-04-29 7:36 Rupert Wood
2003-02-15 10:56 Alexey V. Neyman
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=20030518124600.29833.qmail@sources.redhat.com \
--to=jeff@thecreems.com \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).