Date: Wed, 11 Nov 1998 11:56:17 -0500 From: "Yarema" <yds@ingress.net> To: "Thomas Gellekum" <tg@ihf.rwth-aachen.de> Cc: <freebsd-ports@FreeBSD.ORG> Subject: Re: ports/8636: configure for python-1.5.1 thinks cc is a cross compiler Message-ID: <00c301be0d94$332164e0$1f40e6cd@ichiban.ingress.com>
next in thread | raw e-mail | index | archive | help
Nevermind, thanks for the help though. It was my goof. I did a buildworld with optimizations other than -O. It caused me a bit of grief the PR below being one of them. After setting CFLAGS= -pipe -O and doing another buildworld the problem below went away. I learned my lesson... <sheepish grin> -- Yarema -----Original Message----- From: Thomas Gellekum <tg@ihf.rwth-aachen.de> To: Yarema <yds@ingress.net> Date: Wednesday, November 11, 1998 10:44 AM Subject: Re: ports/8636: configure for python-1.5.1 thinks cc is a cross compiler >Yarema <yds@ingress.net> writes: > >> As requested this is the entire config.log file: >> >> This file contains any messages produced by compilers while >> running configure, to aid debugging if configure makes a mistake. >> >> configure:589: checking MACHDEP >> configure:634: checking CCC >> configure:649: checking for --without-gcc >> configure:683: checking for gcc >> configure:760: checking whether the C compiler >> (cc -pipe -O2 -D_THREAD_SAFE -pthread -rdynamic) works >> configure:774: cc -o onftest -pipe -O2 -D_THREAD_SAFE -pthread -rdynamic >> conftest.c 1>&5 >> configure:794: checking whether the C compiler >> (cc -pipe -O2 -D_THREAD_SAFE -pthread -rdynamic) is a cross-compiler > >Here's the relevant code from configure: > >cat > conftest.$ac_ext <<EOF >#line 770 "configure" >#include "confdefs.h" >main(){return(0);} >EOF >if { (eval echo configure:774: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest; then > ac_cv_prog_cc_works=yes > # If we can't run a trivial program, we are probably using a cross compiler. > if (./conftest; exit) 2>/dev/null; then > ac_cv_prog_cc_cross=no > else > ac_cv_prog_cc_cross=yes > fi >else > >Your output means that the (eval $ac_link) worked fine, but >(./conftest; exit) returned something different than 0. Could you >check this by hand, like this: > >tmp:228) cc -o conftest conftest.c >tmp:229) (./conftest; exit) >tmp:230) echo $? >0 > >> BTW, confdefs.h is only 1 byte at this point. > >This is normal, confdefs.h contains only a newline. > >tg > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?00c301be0d94$332164e0$1f40e6cd>