Cc signal 10
Matthew Dillon
dillon at apollo.backplane.com
Thu Dec 11 10:20:21 PST 2003
:Sources of this morning are now bailing during buildworld with signal 10
:errors. I wonder if this is related to the propolice stuff ?
:
:cc -fpic -DPIC -O -pipe -march=pentiumpro -DTERMIOS -DANSI_SOURCE
:-I/usr/src/secure/lib/libcrypto/../../../crypto/openssl
:-I/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto
:-I/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/engine
:-I/usr/obj/usr/src/secure/lib/libcrypto -DL_ENDIAN -c
:/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/x509/x509_d2.c
:-o
:x509_d2.So
:cc: Internal compiler error: program cc1 got fatal signal 10
:cpp0: output pipe has been closed
:*** Error code 1
:
:Stop in /usr/src/secure/lib/libcrypto.
:*** Error code 1
:
:---------------------------------------
:Robin P. Blanchard
I'm doing a full buildworld/installworld/buildworld sequence to
find out.
Does it reliably fail at the same place every time? If not then
it is not likely to be a compiler problem. If so then it is likely
to be a compiler problem.
-Matt
Matthew Dillon
<dillon at xxxxxxxxxxxxx>
More information about the Bugs
mailing list