From owner-freebsd-ports Wed Nov 11 10:43:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA18675 for freebsd-ports-outgoing; Wed, 11 Nov 1998 10:43:15 -0800 (PST) (envelope-from owner-freebsd-ports@FreeBSD.ORG) Received: from paris.dppl.com (paris.dppl.com [205.230.74.150]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA18668 for ; Wed, 11 Nov 1998 10:43:13 -0800 (PST) (envelope-from yds@ingress.net) Received: (qmail 5554 invoked from network); 11 Nov 1998 16:56:13 -0000 Received: from ichiban.ingress.com (HELO ichiban) (205.230.64.31) by paris.dppl.com with SMTP; 11 Nov 1998 16:56:13 -0000 Message-ID: <00c301be0d94$332164e0$1f40e6cd@ichiban.ingress.com> From: "Yarema" To: "Thomas Gellekum" Cc: Subject: Re: ports/8636: configure for python-1.5.1 thinks cc is a cross compiler Date: Wed, 11 Nov 1998 11:56:17 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 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... -- Yarema -----Original Message----- From: Thomas Gellekum To: Yarema 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 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 <#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