> 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
[
Seems others have had this debate over package managers as well. The
difference is someone has gone and done something about it :)
This article on freshmeat:
http://freshmeat.net/news/2000/12/02/975819599.html
details how they decided that apt-get was the best for actual package
ma
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
>
> *
