public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Joel Sherrill <joel.sherrill@OARcorp.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: ada/8344: mips-rtems build problem
Date: Mon, 12 May 2003 13:56:00 -0000 [thread overview]
Message-ID: <20030512135602.28829.qmail@sources.redhat.com> (raw)
The following reply was made to PR ada/8344; it has been noted by GNATS.
From: Joel Sherrill <joel.sherrill@OARcorp.com>
To: Laurent GUERBY <guerby@acm.org>
Cc: Dara Hazeghi <dhazeghi@yahoo.com>, gcc-gnats@gcc.gnu.org,
nobody@gcc.gnu.org, joel@OARcorp.com
Subject: Re: ada/8344: mips-rtems build problem
Date: Mon, 12 May 2003 08:54:08 -0500
Laurent GUERBY wrote:
>
> On Fri, 2003-05-09 at 21:02, Dara Hazeghi wrote:
> > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-
> > trail&database=gcc&pr=8344
> >
> > Hello,
> >
> > this PR lists a number of patches that appear to have been applied. Is
> > this so? If so, can anyone confirm that the bug in question no longer
> > appears? Thanks,
>
> The problem (ada/final.c => ada/adafinal.c) has been fixed for 3.2, 3.3
> branches, mainline and ACT sources, I'm closing it, thanks for reminding
> us.
Laurent is correct. This is fixed and we incldue Ada in the mips-rtems
RPMs. Sorry this was still open.
> Laurent
--
Joel Sherrill, Ph.D. Director of Research & Development
joel@OARcorp.com On-Line Applications Research
Ask me about RTEMS: a free RTOS Huntsville AL 35805
Support Available (256) 722-9985
next reply other threads:[~2003-05-12 13:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-12 13:56 Joel Sherrill [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-09 19:16 Laurent GUERBY
2003-05-09 19:08 guerby
2003-05-09 19:06 Dara Hazeghi
2003-01-13 14:25 joel
2002-10-24 14:56 joel
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=20030512135602.28829.qmail@sources.redhat.com \
--to=joel.sherrill@oarcorp.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).