kern/123940: [build] FreeBSD 7-STABLE buildworld fails with internal gcc error (no HW problem!)

[Kris Kennaway]

The following reply was made to PR kern/123940; it has been noted by GNATS.

From: Kris Kennaway <kris at FreeBSD.org>
To: Lev Serebryakov <lev at FreeBSD.org>
Cc: bug-followup at FreeBSD.org, Kris Kennaway <kris at FreeBSD.org>,
	vwe at FreeBSD.org
Subject: Re: kern/123940: [build] FreeBSD 7-STABLE buildworld fails with internal gcc error (no HW problem!)
Date: Sat, 24 May 2008 08:26:28 +0000

 On Sat, May 24, 2008 at 09:38:47AM +0400, Lev Serebryakov wrote:
 > Hello, bug-followup.
 > 
 > gcc version is system one:
 > 
 > blob# gcc -v
 > Using built-in specs.
 > Target: amd64-undermydesk-freebsd
 > Configured with: FreeBSD/amd64 system compiler
 > Thread model: posix
 > gcc version 4.2.1 20070719  [FreeBSD]
 > blob#
 > 
 > There are NO gcc-related ports installed.
 > 
 > ============== /etc/make.conf
 > # For local ports building
 > WRKDIRPREFIX=/usr/local/build-area/ports
 > WITHOUT_X=YES
 > WITHOUT_X11=YES
 > WITHOUT_GUI=YES
 > 
 > # Global
 > CPUTYPE?=core2
 > 
 > # added by use.perl 2008-05-14 23:54:55
 > PERL_VER=5.8.8
 > PERL_VERSION=5.8.8
 > ============== /etc/make.conf
 > 
 > Here is no /etc/src.conf at all.
 > 
 > Only `makeoptions' in kernel config is:
 > 
 > =======================================
 > makeoptions DEBUG=-g
 > =======================================
 > 
 > memory was tested with 24 hours run of memtest86+ (no errors)
 > disk was tested with 5 runs of fullscan of MHDD + full scan of
 > manufacturer utility, there is NO errors in S.M.A.R.T. attributes and
 > NO old errors in S.M.A.R.T. error log (checked with smartmontools).
 > 
 > filesystem is clean on boot, and shutdown/boot cycle doesn't show any
 > problems with it (/usr/obj is same FS, as /usr)
 > 
 > Temperature of CPU is contorlled with coretemp(4) and is about
 > 40(+/-2) DegC on both cores at `hardest' momemnts, temperature of HDD
 > is controleld with smartd from smartmontools and never raised more than 35 DegC.
 
 Hardware problems by their very nature can be subtle and hard to track
 down.  Sometimes it might take a combination of things to occur before
 the fault happens (e.g. to push power load over the level at which
 your power supply can maintain it), and testing individual components
 will not show the fault.
 
 > Now I'm trying, does setting MAKEOBJDIRPREFIX to non-default value, but
 > on same FS, help.
 
 MAKEOBJDIRPREFIX is used by many people, it does not cause problems of
 this nature.
 
 Kris
 
 --
 In God we Trust -- all others must submit an X.509 certificate.
     -- Charles Forsythe <forsythe at alum.mit.edu>