Huh, I removed '-O' switch from ${CFLAGS} and managed to rebuild
and reinstall gcc. This new (in fact the same) gcc now works fine both
with '-O' and without it. Looks like a pilot error. Strange, anyway.
Sorry to bother you all.

On Sun, Jan 21, 2001 at 02:50:48PM +0300, Alex Kapranoff wrote:
> I have -CURRENT on a UP P166 box.
> I've just managed to build a new kernel and world (cvsuped yesterday)
> and installed them both. Now I get:
> cc: Internal compiler error: program cc1 got fatal signal 11
> *** Error code 1
> Stop in /usr/home/alex/work/own.
> whenever I want to compile something not so trivial as `hello world'.
> So, am I stuck in this situation? I cannot build neither kernel nor
> gcc now. Are there any ways out? Unfortunately, I don't backup system
> binaries, libs or headers.
> How can I debug this? BTW, other big programs such as INN, apache +
> mod_php4 work like a charm.

Alex Kapranoff,                              Voice: +7(0832)791845
We've lived 2 weeks in the brand new millenium...

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to