Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
X-Sent: 26 Mar 2001 19:12:50 GMT
Message-ID: <011a01c0b629$16be0480$28cd00c7@lucent.com>
From: "Christopher Currie" <christopher AT currie DOT com>
To: <cygwin AT cygwin DOT com>
Subject: RE: ./configure problem
Date: Mon, 26 Mar 2001 14:14:58 -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 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400

All,

I searched the archive for problems similar to mine, and I've seen a brief
blurb about problems with configure, but I'm not sure if I've found any
answers. For the past few days, configure scripts that have worked just fine
in the past are starting to error out when trying to build a test
executable. Output logs are at the end of this email.

I've tracked the problem down to a workaround in the default configure
script where the line

'echo > confdefs.h'

appears, apparently used to prevent an error under AIX. This line is a part
of the default configure boilerplate that autoconf generates. Commenting out
the line will allow configure to complete successfully.

With the line intact, my confdefs.h file looks as follows, after this error:

^@#define PACKAGE "foo"
#define VERSION "1.0"

So it appears that this echo command is sticking in something unwanted.
Unfortunately, I have been unable to write a shell script that will
reproduce the problem, but packages I've downloaded off the net have also
exhibited this behavior.

Any assistance would be greatly appreciated.

Christopher Currie

Outputs:

$ ./configure
creating cache ./config.cache
checking for a BSD compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for mawk... no
checking for gawk... gawk
checking whether make sets ${MAKE}... yes
checking for mawk... (cached) gawk
checking for gcc... gcc
checking whether the C compiler (gcc  ) works... no
configure: error: installation or configuration problem: C compiler cannot
create executables.

$ cat config.log
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

configure:559: checking for a BSD compatible install
configure:612: checking whether build environment is sane
configure:685: checking for mawk
configure:685: checking for gawk
configure:715: checking whether make sets ${MAKE}
configure:843: checking for mawk
configure:875: checking for gcc
configure:988: checking whether the C compiler (gcc  ) works
configure:1004: gcc -o conftest    conftest.c  1>&5
In file included from configure:999:
confdefs.h:1: parse error at null character
configure: failed program was:

#line 999 "configure"
#include "confdefs.h"

main(){return(0);}


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple