ccache on amd64

Mel fbsd.questions at
Wed Sep 24 10:24:15 UTC 2008

On Wednesday 24 September 2008 05:34:22 Brian wrote:

> /usr/local/libexec/ccache/world-cc -m32 -march=athlon64 -mfancy-math-387
> -DCOMPAT_32BIT -iprefix /usr/obj/usr/src/lib32/usr/
> -L/usr/obj/usr/src/lib32/usr/lib32 -B/usr/obj/usr/src/lib32/usr/lib32
> -fpic -DPIC -O2 -fno-strict-aliasing -pipe -DTERMIOS -DANSI_SOURCE
> -I/usr/src/secure/lib/libcrypto/../../../crypto/openssl
> -I/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto
> -I/usr/obj/lib32/usr/src/secure/lib/libcrypto -DOPENSSL_THREADS
> -std=gnu89  -c
> /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/x509v3/v3err.c
> -o v3err.So
> building shared library
> Segmentation fault (core dumped)
> *** Error code 139

And this all just works if you set NOCCACHE? Or does the problem persist then?


Problem with today's modular software: they start with the modules
    and never get to the software part.

More information about the freebsd-questions mailing list