Re: my attempt to compile glibc

[Steve Dunham <dunham@cps.msu.edu>]

Davide Barbieri <paci@chiara.dei.unipd.it> writes:

> Juan Cespedes wrote:
>  > On Mon, 27 Oct 1997, Davide Barbieri wrote:
>  > > gcc: Internal compiler error: program cc1 got fatal signal 11
>  > > make[3]: *** [/home/paci/libc-970928/builddir/math/s_ldexp.os] Error 1
>  > > make[3]: Leaving directory `/home/paci/libc-970928/math'
>  > > make[2]: *** [math/subdir_lib] Error 2
>  > > make[2]: Leaving directory `/home/paci/libc-970928'
>  > > make[1]: *** [all] Error 2
>  > > make[1]: Leaving directory `/home/paci/libc-970928/builddir'
>  > > make: *** [build] Error 2

>  > 	Signal 11?  Then, there isn't any problem with that glibc
>  > sources.  signal 11 in gcc means one of these things:

>  > 	4. Hardware problem

> don't know, but this machine had no problem at all, in the past

> with gcc 2.7.1:
> cpp: output pipe has been closed
> gcc: Internal compiler error: program cpp got fatal signal 13
> make[3]: *** [/home/paci/libc-970928/builddir/math/s_fpclassifyf.d] Error 139
> make[3]: Leaving directory `/home/paci/libc-970928/math'
> make[2]: *** [math/subdir_lib] Error 2
> make[2]: Leaving directory `/home/paci/libc-970928'
> make[1]: *** [all] Error 2
> make[1]: Leaving directory `/home/paci/libc-970928/builddir'
> make: *** [build] Error 2

Hmm, different point, different signal  (this one is SIGPIPE). 

Does it fail in the same spot every time you compile it with a given
gcc (e.g. 2.7.3)?

Have you tried compiling a kernel recently?

Are you running out of memory?


Steve
dunham@cps.msu.edu



--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-sparc-request@lists.debian.org . 
Trouble?  e-mail to templin@bucknell.edu .