public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dave at hiauly1 dot hia dot nrc dot ca" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/24822] make[2]: *** [ada/einfo.h] Error 1
Date: Mon, 12 Dec 2005 22:50:00 -0000 [thread overview]
Message-ID: <20051212225052.27778.qmail@sourceware.org> (raw)
In-Reply-To: <bug-24822-276@http.gcc.gnu.org/bugzilla/>
------- Comment #5 from dave at hiauly1 dot hia dot nrc dot ca 2005-12-12 22:50 -------
Subject: Re: make[2]: *** [ada/einfo.h] Error 1
> > > If the issue is with the bootstrap compiler, there's not much we can do.
> >
> > Bootstrap compiler is GCC. This doesn't occur on linux, but it
>
> Well sure, you can't bootstrap GNAT with anything else than GCC ;-)
>
> Is this the same version of GCC ? Could you try with another version ?
The error doesn't occur with 3.4.4. I have a build of 4.1.0 underway.
If the build is successful, I will install and test it to see if the
miscompilation is still present with 4.1. There was a recent fix that
should make debugging easier.
Is GNAT still being maintained in the 4.0 branch?
Dave
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24822
next prev parent reply other threads:[~2005-12-12 22:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-12 16:51 [Bug ada/24822] New: " danglin at gcc dot gnu dot org
2005-12-12 14:52 ` [Bug ada/24822] " charlet at gcc dot gnu dot org
2005-12-12 15:55 ` dave at hiauly1 dot hia dot nrc dot ca
2005-12-12 16:06 ` charlet at adacore dot com
2005-12-12 16:06 ` charlet at gcc dot gnu dot org
2005-12-12 16:08 ` charlet at adacore dot com
2005-12-12 22:50 ` dave at hiauly1 dot hia dot nrc dot ca [this message]
2005-12-13 7:22 ` charlet at adacore dot com
2006-02-05 18:09 ` danglin at gcc dot gnu dot org
2006-03-08 15:27 ` charlet at gcc dot gnu dot org
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=20051212225052.27778.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).