public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Rupert Wood" <Rupert.Wood@softwire.co.uk>
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: Tue, 29 Apr 2003 07:36:00 -0000	[thread overview]
Message-ID: <20030429073600.29185.qmail@sources.redhat.com> (raw)

The following reply was made to PR ada/8689; it has been noted by GNATS.

From: "Rupert Wood" <Rupert.Wood@softwire.co.uk>
To: "Alexey V. Neyman" <alex.neyman@auriga.ru>,
	<gcc-gnats@gcc.gnu.org>,
	<jeff@thecreems.com>,
	<gcc-bugs@gcc.gnu.org>,
	<nobody@gcc.gnu.org>
Cc: "Carl B. Constantine" <cconstan@csc.UVic.CA>
Subject: RE: ada/8689: GNAT 3.15p can not be used as 3.2.1 (others?) boostrap
Date: Tue, 29 Apr 2003 08:33:13 +0100

 On 15th February, Alexy V. Netman wrote:
 
 > I've encountered the same problem. Alexandre Makeev <sonni at mail
 > dot ru> sent me a patch, and having applied it, I was able to
 > bootstrap gcc-3.2.2 with GNAT 3.15p successfully. If there's
 > interest, please contact me and I'll submit it.
 
 This has just cropped up on the gcc-help mailing list. I've reproduced
 this with both the gcc-3.2.3 release and the 3.2 branch from CVS on
 sparc-sun-solaris2.8. The install docs suggest this *should* work.
 Similarly the 3.1 branch fails but the 3.3 branch looks OK.
 
 Is there a good reason that this shouldn't be fixed?
 
 Thanks,
 Rup.


             reply	other threads:[~2003-04-29  7:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-29  7:36 Rupert Wood [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-18 12:46 Jeffrey Creem
2003-05-18  1:06 Jeffrey Creem
2003-05-13  6:35 steven
2003-05-13  0:06 Dara Hazeghi
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=20030429073600.29185.qmail@sources.redhat.com \
    --to=rupert.wood@softwire.co.uk \
    --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).