Which machine? I had oodles of problems (as did others) with RH 7.0
compiling 2.2 well, *any* kernel. Finally had to "downgrade" my gcc,
as well as some include files. OTOH, if this isn't an RH 7.0 box, what is
it? How does it differ from the other machines on which you had no
problems com
[EMAIL PROTECTED] writes:
> In my experience parallel builds normally work very
> well and can yield a huge speedup by having other
> compiles ready to run when one gets I/O bound, but I've
> seen it fail often enough that I'm always willing
> to back off and do a single threaded build as a
> sa
On Sun, 3 Dec 2000, Karl J. Runge wrote:
> Yes, if compiling had been working fine before, this is likely memory
> going bad.
>
> However, for my wife's new machine I found the solution to this same
> sig11 problem was to dial the Motherboard speed down from 100 MHz to 66
> MHz with the machine w
> Yes, if compiling had been working fine before, this is likely memory
> going bad.
I've also seen errors such as this when you run out of swap. A malloc
request fails and if the code doesn't check the return, you get the
sigsegv dereferencing a bad pointer.
FWIW,
Pat
--
Patrick O'Rourke
[
On Sun, 3 Dec 2000, mike ledoux <[EMAIL PROTECTED]> wrote:
> On Sat, 2 Dec 2000, dsbelile wrote:
>
> >anyone know what the hell is going on here ? ive never seen an error
> >like this. is my compiler crapping out ? maybe im just really tired. im
> >running 2.2.17 on other machines and had no pr
I believe that I have occasionally have seen similar
problems doing parallel builds - if you're not doing a
strictly single threaded build you might want to give
it another try and be sure your concurrency factor
(the maximum allowable number of jobs you're willing
to permit make to run i.e. th
Jeff Dike wrote:
> [EMAIL PROTECTED] said:
> > cc: Internal compiler error: program cc1 got fatal signal 11
>
> You have some bad memory. Find it and replace it, and kernel builds will work
> a lot better.
>
> Jeff
>
> *
Jeff Dike wrote:
> [EMAIL PROTECTED] said:
> > cc: Internal compiler error: program cc1 got fatal signal 11
>
> You have some bad memory. Find it and replace it, and kernel builds will work
> a lot better.
>
> Jeff
>
> *
[EMAIL PROTECTED] said:
> cc: Internal compiler error: program cc1 got fatal signal 11
You have some bad memory. Find it and replace it, and kernel builds will work
a lot better.
Jeff
**
To unsubscribe
anyone know what the hell is going on here ? ive never seen an error
like this. is my compiler crapping out ? maybe im just really tired. im
running 2.2.17 on other machines and had no problem till now. here is
the error :
cc -D__KERNEL__ -I/usr/src/linux-2.2.17/include -Wall
-Wstrict-prototypes
10 matches
Mail list logo
