On Tue, Dec 12, 2000 at 01:07:04PM -0800, Pete Lypkie wrote:
> First of all, i believe you should compile 2.2.17 with gcc version 2.7.2
I compile my 2.2 kernels with gcc 2.95.2, no problem.
hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
On Tue, Dec 12, 2000 at 01:07:04PM -0800, Pete Lypkie wrote:
> First of all, i believe you should compile 2.2.17 with gcc version 2.7.2
I compile my 2.2 kernels with gcc 2.95.2, no problem.
hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [
I used to get this error many years ago on a Cyrix processor with redhat 4.
Redhat had a patch for it. Are you running a Cyrix processor?
On Tue, Dec 12, 2000 at 11:30:19PM +0100, Adrian Bunk wrote:
> On Tue, 12 Dec 2000, Pete Lypkie wrote:
>
> >...
> > > gcc2.95.2-20
> >...
> > Fir
It turns out it was an overclocked cpu problem. Thanks for the all
help, I guess I will have to get a bigger fan, before I can really
overclock my AMD350. You cannot imagen the weight off my shoulders now
that I can compile again. I was sceptical about it being my memory
because my 128MB 16x64 D
On Tue, 12 Dec 2000, Pete Lypkie wrote:
>...
> > gcc2.95.2-20
>...
> First of all, i believe you should compile 2.2.17 with gcc version 2.7.2
>
> you can install it from the package called "gcc272".
>
> IIRC, the 2.4 series has moved to using gcc 2.95, but 2.2 still needs gcc
> 2.7.2
>
other. Some of then take over fifty times running make bzImage before
> the process moves on.
> cc: Internal compiler error: program cc1 got fatal signal 11
>
> By running the command that it barfed on, some times it too returns the
> same error, other times it successed.
>
> C
Some of then take over fifty times running make bzImage before
> the process moves on.
> cc: Internal compiler error: program cc1 got fatal signal 11
>
> By running the command that it barfed on, some times it too returns the
> same error, other times it successed.
Almost cert
I used to get this error many years ago on a Cyrix processor with redhat 4. Redhat
had a patch for it. Are you running a Cyrix processor?
On Tue, Dec 12, 2000 at 11:30:19PM +0100, Adrian Bunk wrote:
> On Tue, 12 Dec 2000, Pete Lypkie wrote:
>
> >...
> > > gcc2.95.2-20
> >...
> > Fi
On 12-Dec-2000 James Leigh wrote:
> Can anybody tell me why I get this error so _much_ when I am compiling a
> kernel?
>
> I litteraly get it hundreds of times (seriously). I wrote a script that
> gives up after 256 errors, and I it still times outs.
>
please take this to debian-user, debian-m
h.
Or it might just be some faulty RAM on your system.
[snip]
> another. Some of then take over fifty times running make bzImage before
> the process moves on.
>
> cc: Internal compiler error: program cc1 got fatal signal 11
>
> By running the command that it barfed on, some
It turns out it was an overclocked cpu problem. Thanks for the all
help, I guess I will have to get a bigger fan, before I can really
overclock my AMD350. You cannot imagen the weight off my shoulders now
that I can compile again. I was sceptical about it being my memory
because my 128MB 16x64
On Wed, Dec 13, 2000 at 01:15:35AM +0500, James Leigh wrote:
>
> I am using debian woody with kernel 2.2.17.
> I do have bin86 installed and these other programs too:
> gcc2.95.2-20
> make 3.79.1-1
> bin86 0.15.3-1
> binutils 2.10.1.0.2-1
> bzip2 1.0.1
James Leigh <[EMAIL PROTECTED]> wrote:
>Can anybody tell me why I get this error so _much_ when I am compiling a
>kernel?
[...]
>cc: Internal compiler error: program cc1 got fatal signal 11
Chances are you've got hardware problems, probably bad memory. See
http://ww
kernel. This is the error I always get. It seems that it
returns the error for almost every f*n *.c file in there, one after
another. Some of then take over fifty times running make bzImage before
the process moves on.
cc: Internal compiler error: program cc1 got fatal signal 11
By running the
On Tue, 12 Dec 2000, Pete Lypkie wrote:
>...
> > gcc2.95.2-20
>...
> First of all, i believe you should compile 2.2.17 with gcc version 2.7.2
>
> you can install it from the package called "gcc272".
>
> IIRC, the 2.4 series has moved to using gcc 2.95, but 2.2 still needs gcc
> 2.7.2
other. Some of then take over fifty times running make bzImage before
> the process moves on.
> cc: Internal compiler error: program cc1 got fatal signal 11
>
> By running the command that it barfed on, some times it too returns the
> same error, other times it successed.
>
> C
Some of then take over fifty times running make bzImage before
> the process moves on.
> cc: Internal compiler error: program cc1 got fatal signal 11
>
> By running the command that it barfed on, some times it too returns the
> same error, other times it successed.
Almost cert
On 12-Dec-2000 James Leigh wrote:
> Can anybody tell me why I get this error so _much_ when I am compiling a
> kernel?
>
> I litteraly get it hundreds of times (seriously). I wrote a script that
> gives up after 256 errors, and I it still times outs.
>
please take this to debian-user, debian-
h.
Or it might just be some faulty RAM on your system.
[snip]
> another. Some of then take over fifty times running make bzImage before
> the process moves on.
>
> cc: Internal compiler error: program cc1 got fatal signal 11
>
> By running the command that it barfed on, some
On Wed, Dec 13, 2000 at 01:15:35AM +0500, James Leigh wrote:
>
> I am using debian woody with kernel 2.2.17.
> I do have bin86 installed and these other programs too:
> gcc2.95.2-20
> make 3.79.1-1
> bin86 0.15.3-1
> binutils 2.10.1.0.2-1
> bzip2 1.0.
James Leigh <[EMAIL PROTECTED]> wrote:
>Can anybody tell me why I get this error so _much_ when I am compiling a
>kernel?
[...]
>cc: Internal compiler error: program cc1 got fatal signal 11
Chances are you've got hardware problems, probably bad memory. See
http://ww
kernel. This is the error I always get. It seems that it
returns the error for almost every f*n *.c file in there, one after
another. Some of then take over fifty times running make bzImage before
the process moves on.
cc: Internal compiler error: program cc1 got fatal signal 11
By running the
22 matches
Mail list logo
