From: _hate_spam_thunder7@xs4all.nl (jwk)
To: help-gcc@gnu.org
Subject: Re: Internal compiler error
Date: Thu, 30 Sep 1999 03:33:00 -0000 [thread overview]
Message-ID: <slrn7v5t1d.1c3._hate_spam_thunder7@middle.of.nowhere> (raw)
In-Reply-To: <37F26D1D.5D0D6500@sdf.lonestar.org>
On Wed, 29 Sep 1999 15:48:45 -0400, Guardian
<guardianNOSTUFF@sdf.lonestar.org> wrote:
>Comments: Buggy compiler, how to compile a compiler with a buggy
>compiler, what do I need to upgrade on Slackware 4.0
>
>xgcc: Internal compiler error: program cc1 got fatal signal 11
>make[2]: *** [cccp.o] Error 1
There is a sig11-HowTo floating around (try ftpsearch to retrieve it)
which says it is *almost always* a hardware fault (bad ram, overclocked
CPU, fan failure etc) but I can attest from personal experience that if
it happens during make bootstrap *and always at exactly the same point*
it may also be your libc-libraries and your libc-header files are not
compatible.....
Jurriaan
--
proof by intimidation:
'Trivial'.
WARNING: multiple messages have this Message-ID
From: _hate_spam_thunder7@xs4all.nl (jwk)
To: help-gcc@gnu.org
Subject: Re: Internal compiler error
Date: Thu, 30 Sep 1999 23:56:00 -0000 [thread overview]
Message-ID: <slrn7v5t1d.1c3._hate_spam_thunder7@middle.of.nowhere> (raw)
Message-ID: <19990930235600.z8uDsNsEigYmRCUK6VPkFyF7bbIi_4KeTx4_aHvH5ZE@z> (raw)
In-Reply-To: <37F26D1D.5D0D6500@sdf.lonestar.org>
On Wed, 29 Sep 1999 15:48:45 -0400, Guardian
<guardianNOSTUFF@sdf.lonestar.org> wrote:
>Comments: Buggy compiler, how to compile a compiler with a buggy
>compiler, what do I need to upgrade on Slackware 4.0
>
>xgcc: Internal compiler error: program cc1 got fatal signal 11
>make[2]: *** [cccp.o] Error 1
There is a sig11-HowTo floating around (try ftpsearch to retrieve it)
which says it is *almost always* a hardware fault (bad ram, overclocked
CPU, fan failure etc) but I can attest from personal experience that if
it happens during make bootstrap *and always at exactly the same point*
it may also be your libc-libraries and your libc-header files are not
compatible.....
Jurriaan
--
proof by intimidation:
'Trivial'.
WARNING: multiple messages have this Message-ID
From: _hate_spam_thunder7@xs4all.nl (jwk)
To: help-gcc@gnu.org
Subject: Re: Internal compiler error
Date: Fri, 01 Oct 1999 00:00:00 -0000 [thread overview]
Message-ID: <slrn7v5t1d.1c3._hate_spam_thunder7@middle.of.nowhere> (raw)
Message-ID: <19991001000000.jFFZK6c0YfuF1YgnLF1PE86prsGdrLCBznJuC5Hn3wE@z> (raw)
In-Reply-To: <37F26D1D.5D0D6500@sdf.lonestar.org>
On Wed, 29 Sep 1999 15:48:45 -0400, Guardian
<guardianNOSTUFF@sdf.lonestar.org> wrote:
>Comments: Buggy compiler, how to compile a compiler with a buggy
>compiler, what do I need to upgrade on Slackware 4.0
>
>xgcc: Internal compiler error: program cc1 got fatal signal 11
>make[2]: *** [cccp.o] Error 1
There is a sig11-HowTo floating around (try ftpsearch to retrieve it)
which says it is *almost always* a hardware fault (bad ram, overclocked
CPU, fan failure etc) but I can attest from personal experience that if
it happens during make bootstrap *and always at exactly the same point*
it may also be your libc-libraries and your libc-header files are not
compatible.....
Jurriaan
--
proof by intimidation:
'Trivial'.
next prev parent reply other threads:[~1999-09-30 3:33 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-29 12:58 Guardian
1999-09-30 3:33 ` jwk [this message]
1999-09-30 23:56 ` jwk
1999-10-01 0:00 ` jwk
1999-10-01 13:49 ` Guardian
1999-10-31 13:57 ` Guardian
1999-09-30 23:56 ` Guardian
1999-10-01 0:00 ` Guardian
2001-07-02 8:04 Av Vl
2001-07-03 8:36 Av Vl
2003-07-30 20:29 DEEPA SIVASANKARANE
2008-02-29 21:27 internal " raian.ufop
2008-02-29 22:16 ` Brian Dessent
2008-03-03 18:50 ` raian.ufop
2010-07-12 9:04 Malte.Mauelshagen
2010-07-12 9:56 ` Ian Lance Taylor
2012-12-24 16:44 Internal Compiler Error tanle
2012-12-24 18:19 ` Andrew Haley
2012-12-27 17:27 ` Iyer, Balaji V
2018-01-19 13:17 internal compiler error Matt Sexton via gcc-help
2018-01-19 13:26 ` Mikhail Maltsev
2018-01-19 14:35 ` Matt Sexton via gcc-help
2018-01-19 15:54 ` Matt Sexton via gcc-help
2018-01-22 13:14 ` Mason
2018-01-22 13:21 ` Matt Sexton via gcc-help
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=slrn7v5t1d.1c3._hate_spam_thunder7@middle.of.nowhere \
--to=_hate_spam_thunder7@xs4all.nl \
--cc=help-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).