[erlang-questions] Error building R12B-4 on SPARC T1

[Vance Shipley]

New T1000, new Solaris 10 5/09, new Erlang R13B01, same problem.

I can't be the only one experiencing this.

	-Vance

On Sun, Sep 14, 2008 at 10:31:11AM +0200, Mikael Pettersson wrote:
}  Vance Shipley writes:
}   > Building R12B-4 is failing for me on a Sun T1000 server:
}   > 
}   >    gcc  -g  -O3 -fomit-frame-pointer
}   >    -I/usr/local/src/otp_src_R12B-4/erts/sparc-sun-solaris2.10
}   >    -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64  -DERTS_SMP -DHAVE_CONFIG_H
}   >    -Wall -Wstrict-prototypes -Wmissing-prototypes
}   >    -Wdeclaration-after-statement -DUSE_THREADS -D_THREAD_SAFE -D_REENTRANT
}   >    -D_POSIX_PTHREAD_SEMANTICS -Wa,-xarch=v8plusa -Ibeam -Isys/unix
}   >    -Isys/common -Isparc-sun-solaris2.10/opt/smp -Isparc-sun-solaris2.10
}   >    -Izlib -Ipcre -Ihipe -I../include/internal
}   >    -I../include/internal/sparc-sun-solaris2.10 -c beam/erl_bif_info.c -o
}   >    obj/sparc-sun-solaris2.10/opt/smp/erl_bif_info.o
}   >    gcc: Internal error: Segmentation Fault (program cg)
}   >    Please submit a full bug report to
}   >     <URL:http://forum.java.sun.com/forum.jspa?forumID=905>.
}   >    make[3]: *** [obj/sparc-sun-solaris2.10/opt/smp/erl_bif_info.o] Error 1
}   >    make[3]: Leaving directory `/usr/local/src/otp_src_R12B-4/erts/emulator'
}   >    make[2]: *** [opt] Error 2
}   >    make[2]: Leaving directory `/usr/local/src/otp_src_R12B-4/erts/emulator'
}   >    make[1]: *** [smp] Error 2
}   >    make[1]: Leaving directory `/usr/local/src/otp_src_R12B-4/erts'
}   >    gmake: *** [emulator] Error 2
}   > 
}   > This is using SUNWgccfss v4.2.0 although it failed identically with v4.0.3.
}   > I did submit a bug report to Sun as suggested.
}  
}  I've just built R12B-4 on Solaris/SPARC with gcc-4.3.2, gcc-4.2.4,
}  and gcc-4.0.4, and none of them ICEd like your GCCs do.
}  
}  However:
}  - I compiled my GCCs myself from vanilla release tarballs
}  - our departmental Suns run Solaris 9 not 10 as your T1000 does
}  - after years of usage we know our Suns have good HW
}  
}  The breakage could be in SUNWgccfss, or Solaris 10 (do you have
}  all OS updates?), or your T1000 might have developed a HW problem
}  like bad RAM or broken cache.
}  
}  You could test with the same SUNWgccfss on a different machine.
}  If the ICEs persist then you can rule out a HW problem.
}  
}  /Mikael

-- 
	-Vance