On Wednesday 24 September 2008 16:28:44 Brian wrote:
> Mel wrote:
> > 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
> >> -DDSO_DLFCN -DHAVE_DLFCN_H -DOPENSSL_NO_IDEA -DL_ENDIAN -DNO_IDEA
> >> -std=gnu89 -c
> >> /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/x509v3/v3er
> >>r.c -o v3err.So
> >> building shared library libcrypto.so.4
> >> Segmentation fault (core dumped)
> >> *** Error code 139
> >
> > And this all just works if you set NOCCACHE? Or does the problem persist
> > then?
>
> I havebt specifically done the NOCCACHE, but commenting out all the
> ccache stuff out of make.conf and /etc/profile, doing a straight compile
> works.
> Setting cputype=k8 fails as well.
Since it fails on the link, I wonder if the wrong linker is called by ccache.
I'll see what I can find out when it quiets down, right now machine is under
heavy load.
(It might just be the path you set in /etc/profile. I use only
the /etc/make.conf version, not set the path additionally and
make -f /usr/src/Makefile.inc1 -V LIB32WMAKE shows it's mangeling the path)
--
Mel
Problem with today's modular software: they start with the modules
and never get to the software part.
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
