This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: GCC 3.0 Branch Status

Richard Earnshaw wrote:
> > 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 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?

My bootstrap has passed the previous failure without any problem now
(with and without the option: --enble-debug).  So it looks as if the
problem is no longer there.  I'll send a message after both builds
finish, but there should be no real problem.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]