This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: egcs-1998-06-12: bootstrap failure
- To: burley at gnu dot org
- Subject: Re: egcs-1998-06-12: bootstrap failure
- From: Manfred Hollstein <manfred at s-direktnet dot de>
- Date: Sat, 13 Jun 1998 16:10:39 +0200 (MEST)
- Cc: toon at moene dot indiv dot nluug dot nl, mlawson at drfmc dot ceng dot cea dot fr, egcs at cygnus dot com
- References: <9806122123.AA27956@moene.indiv.nluug.nl><199806130740.DAA16317@melange.gnu.org>
- Reply-To: manfred at s-direktnet dot de, Manfred dot Hollstein at ks dot sel dot alcatel dot de
On Sat, 13 June 1998, 03:40:22, burley@gnu.org wrote:
> >../../egcs/gcc/c-lex.c:1445: warning: variable `conversion_errno'
> >might be clobbered by `longjmp' or `vfork'
> >../../egcs/gcc/global.c:401: Internal compiler error in function
> >global_alloc
> >make[2]: *** [c-lex.o] Error 1
> >
> >Note that the error message reports the source file as
> >`../../egcs/gcc/global.c', which is completely bogus, as the compile
> >line above clearly shows that the file being compiled is c-lex.c.
> >
> >Something very fishy is going on here.
>
> Is it at all possible the stderr output you're seeing is "beating"
> the stdout output showing the new compile line? Or that somehow
> you're seeing a strange flushing behavior?
>
> Seems unlikely, given how much later global.c normally is compiled
> after c-lex.c, and that make still reports an error occurring
> for the c-lex.o target. (I wonder whether that report is to
> stdout or stderr?)
>
> So, another possibility might be I/O error or similar, affecting
> any of: the relevant Makefile (c-lex.o fragment, for example);
> the compiler itself; the preprocessor; the OS; etc.
>
> tq vm, (burley)
Well, I'd guess it's just saying `I've got an "internal compiler error"
in function global_alloc at line 401 from file global.c'.
manfred