RELENG_6 does not compile

[Kris Kennaway]

On Fri, Sep 22, 2006 at 02:59:53AM +0200, martinko wrote:
> Kris Kennaway wrote:
> > On Fri, Sep 22, 2006 at 02:40:24AM +0200, martinko wrote:
> >> Kris Kennaway wrote:
> >>> That doesn't provide any information since you used -j4.  When posting
> >>> errors from buildworld, you need to run without -j, or log the entire
> >>> buildworld output and then figure out where the actual error occurred
> >>> (may be thousands of lines from the end).
> >>>
> >>> Kris
> >> here it is again (without -j) :
> >>
> >> echo libssl.so.4: /usr/obj/usr/src/tmp/usr/lib/libcrypto.a >> .depend
> >> cc -O2 -fno-strict-aliasing -pipe -march=pentium-m -DTERMIOS
> >> -DANSI_SOURCE -I/usr/src/secure/lib/libssl/../../../crypto/openssl
> >> -I/usr/src/secure/lib/libssl/../../../crypto/openssl/crypto
> >> -I/usr/obj/usr/src/secure/lib/libssl -DOPENSSL_THREADS -DDSO_DLFCN
> >> -DHAVE_DLFCN_H -DL_ENDIAN  -c
> >> /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/bio_ssl.c
> >> cc -O2 -fno-strict-aliasing -pipe -march=pentium-m -DTERMIOS
> >> -DANSI_SOURCE -I/usr/src/secure/lib/libssl/../../../crypto/openssl
> >> -I/usr/src/secure/lib/libssl/../../../crypto/openssl/crypto
> >> -I/usr/obj/usr/src/secure/lib/libssl -DOPENSSL_THREADS -DDSO_DLFCN
> >> -DHAVE_DLFCN_H -DL_ENDIAN  -c
> >> /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s23_clnt.c
> >> /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s23_clnt.c: In
> >> function `ssl23_connect':
> >> /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s23_clnt.c:216:
> >> internal compiler error: Segmentation fault: 11
> >> Please submit a full bug report,
> >> with preprocessed source if appropriate.
> >> See <URL:http://gcc.gnu.org/bugs.html> for instructions.
> >> *** Error code 1
> > 
> > Chances are you have failing hardware.
> > 
> > Kris
> 
> you must be kidding! :-o
> no, really, this is a laptop and i hope it's not going to die or
> something. :-/
> well, it would actually be better now before the warranty is over. ;-)
> anyway, how did you come to your conclusion pls ??

Such errors are almost always the fault of failing hardware
components; a functioning system does not cause sporadic software
failure.  This comes up about once a week so please search the
archives or google for extensive discussion.

Kris