This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GCC 3.0 Branch Status
- To: "Rod m. Stewart" <rod dot stewart at rebel dot com>
- Subject: Re: GCC 3.0 Branch Status
- From: Richard Earnshaw <rearnsha at arm dot com>
- Date: Mon, 22 Jan 2001 15:43:31 +0000
- cc: rearnsha at arm dot com, Philip Blundell <philb at gnu dot org>, Mark Mitchell <mark at codesourcery dot com>, gcc at gcc dot gnu dot org, stewart at netwinder dot org, Richard dot Earnshaw at arm dot com
- Organization: ARM Ltd.
- Reply-To: rearnsha at arm dot com
> Richard Earnshaw wrote:
>
> > I bootstrapped Friday's sources on my Netwinder without a problem; both
> > with and without checking enabled.
> >
> > What I'm most concerned about is that the autobuild at NetWinder.org is
> > still failing -- it seems to be showing all the hallmarks of using the
> > pre-fixed copy of reload1.c. Rod, can you check that it really is
> > building from the latest sources?
>
> No, it has the latest reload1.c from CVS. It seems to be dying with the
> following error (and looking back, has for a little while). About the
> only major difference I have is I was building with --enable-debug.
> I'll start a build now without that and see how it goes (although it
> will take about 10 hours to complete).
>
> (My machine crashed over the weekend, so I'm just starting today's build
> now.)
>
> Here is the error I've been getting:
Yes, I can see the error from the build logs. Since I can't reproduce
this on my own machine, I'm going to need more information. If it fails
again, can you get me a stack back-trace from gdb?
R.