freebsd stable - Aug 2015 - Buildworld failure on stable

On Wed, Aug 26, 2015 at 10:48:29AM +0100, Matt Smith wrote:
> On Aug 26 11:09, Slawa Olhovchenkov wrote:
> >On Wed, Aug 26, 2015 at 08:01:25AM +0100, Matt Smith wrote:
> >
> >> Trying to do a buildworld from the latest stable seems to result
in a
> >> failure within openssl. Anyone else seen this?
> >>
> >> --- ocsp_ext.o ---
> >> cc   -O2 -pipe   -DTERMIOS -DANSI_SOURCE
> >> -I/usr/src/secure/lib/libcrypto/../../../crypto/openssl
-I/usr/src/secu
> >> re/lib/libcrypto/../../../crypto/openssl/crypto
> >> -I/usr/obj/usr/src/secure/lib/libcrypto -DOPENSSL_THREADS -DDSO_
> >> DLFCN -DHAVE_DLFCN_H -DL_ENDIAN -DOPENSSL_IA32_SSE2 -DAES_ASM
> >> -DBSAES_ASM -DVPAES_ASM -DOPENSSL_BN_ASM_MONT -DOP
> >> ENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DMD5_ASM -DGHASH_ASM
> >> -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DWHIRLPOOL_
> >> ASM
-I/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/asn1
> >> -I/usr/src/secure/lib/libcrypto/../../..
> >> /crypto/openssl/crypto/evp
> >>
-I/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/modes
> >> -std=gnu89 -Qunu
> >> sed-arguments  -fstack-protector -Wno-pointer-sign -Wno-empty-body
> >> -Wno-string-plus-int -Wno-unused-const-variab
> >> le -Wno-tautological-compare -Wno-unused-value
-Wno-parentheses-equality
> >> -Wno-unused-function -Wno-enum-conversi
> >> on -Wno-switch -Wno-switch-enum -Wno-knr-promoted-parameter
> >> -Wno-parentheses -c /usr/src/secure/lib/libcrypto/..
> >> /../../crypto/openssl/crypto/ocsp/ocsp_ext.c -o ocsp_ext.o
> >> --- obj_dat.o ---
> >> cc: error: unable to execute command: Bus error (core dumped)
> >> cc: error: clang frontend command failed due to signal (use -v to
see
> >> invocation)
> >
> >Hardware error or memory exhausted
> 
> It does appear to be something along those lines. It's not memory 
> exhaustion as it has around 2GB free at the point it fails. However
I've
> deleted /usr/obj and started the buildworld again and it failed in a 
> different place with the same error. I'm trying it again without -j4 to
> see what happens. But isn't looking too good. :(
Look like hardware error.
RAM/CPU/MB

On Aug 26 13:10, Slawa Olhovchenkov wrote:
>> >Hardware error or memory exhausted
>>
>> It does appear to be something along those lines. It's not memory
>> exhaustion as it has around 2GB free at the point it fails. However
I've
>> deleted /usr/obj and started the buildworld again and it failed in a
>> different place with the same error. I'm trying it again without
-j4 to
>> see what happens. But isn't looking too good. :(
>
>Look like hardware error.
>RAM/CPU/MB
Interestingly it *always* manages to succesfully compile clang etc and 
it has no issues compiling things from ports. It fails compiling 
something from lib like openssl or kerberos.  Doesn't buildworld build a 
bootstrap version of clang and then use that version to compile the rest 
of it? I might try downgrading my sources back to the version that I 
last succesfully compiled just to prove it one way or the other to 
myself.

-- 
Matt