FREEBSD 5.4 - Internal compiler error: Segmentation fault

[Garrett Cooper]

Richard Crane wrote:

> Hello,
>
> MACHINE SPECS:
> I'm running a SuperServer 6010H with 1 gi of memory and 1 gigahert cpu.
>
> I'm getting an internal compiler error: Segmentation fault when doing 
> a make install clean of cvsup-without-gui.
>
> I RUN THE FOLLOWING COMMANDS:
>
> # cd /usr/ports/net/cvsup-without-gui/
> # make install clean
>
> THE FOLLOWING ARE THE LAST LINES IN THE COMPILATION PROCESS:
>
> ../../gcc/gcc/tree.h:1221: warning: type of bit-field `mode' is a GCC 
> extension
> ../../gcc/gcc/tree.h:1766: warning: type of bit-field `mode' is a GCC 
> extension
> ../../gcc/gcc/tree.h:1791: warning: type of bit-field `built_in_class' 
> is a GCC extension
> ../../gcc/gcc/calls.c: In function `compute_argument_addresses':
> ../../gcc/gcc/calls.c:1693: internal compiler error: Segmentation fault
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <URL:http://gcc.gnu.org/bugs.html> for instructions.
> gmake[1]: *** [calls.o] Error 1
> gmake[1]: Leaving directory 
> `/usr/ports/lang/ezm3/work/ezm3-1.2/language/modula3/m3compiler/m3cc/FreeBSD4/gcc' 
>
> mkdir FreeBSD4
> --- building in FreeBSD4 ---
>
> m3build: quake error: quake error: runtime error: Failed to build m3cc
>
> --procedure--  -line-  -file---
> error              --  <builtin>
>                  112  
> /usr/ports/lang/ezm3/work/ezm3-1.2/language/modula3/m3compiler/m3cc/src/m3makefile 
>
>
>
> m3build: quake error: quake error: runtime error: m3build failed with 
> error code: 1
>
> --procedure--  -line-  -file---
> error              --  <builtin>
> BuildChunk        164  /usr/ports/lang/ezm3/work/ezm3-1.2/src/m3makefile
> PkgInfo           240  /usr/ports/lang/ezm3/work/ezm3-1.2/src/m3makefile
>                   31  /usr/ports/lang/ezm3/work/ezm3-1.2/src/PACKAGES
>
> gmake: *** [packages] Error 1
> *** Error code 2
>
> Stop in /usr/ports/lang/ezm3.
> *** Error code 1
>
> Stop in /usr/ports/net/cvsup-without-gui.

Dunno if this applies to FBSD as well, but in Linux many GCC seg faults 
were caused by either bad programming on someone's behalf, or bad RAM. 
I'd run a RAM test first just to be sure it's not the RAM
-Garrett