X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,RCVD_IN_DNSWL_LOW
X-Spam-Check-By:	sourceware.org
Message-ID:	<4DDBFFFF.8090909@cwilson.fastmail.fm>
Date:	Tue, 24 May 2011 14:59:11 -0400
From:	Charles Wilson <cygwin AT cwilson DOT fastmail DOT fm>
Reply-To:	Charles Wilson <cygwin AT cwilson DOT fastmail DOT fm>
User-Agent:	Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: Error building run2 from source package in win7
References:	<20110523171750 DOT GB16755 AT jethro DOT local DOT lan> <4DDA97CC DOT 1090404 AT redhat DOT com> <4DDAA894 DOT 5090802 AT cwilson DOT fastmail DOT fm> <20110524183824 DOT GA11571 AT jethro DOT local DOT lan>
In-Reply-To:	<20110524183824.GA11571@jethro.local.lan>
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

On 5/24/2011 2:38 PM, David Sastre wrote:

>> hmm...maybe the OP should check his generated config.h file for the
>> offending def.  If it's there, a quick look inside config.log should
>> tell you why 'checking for an ANSI C-conforming const' is reporting 'no'.
> 
> $ grep -nR "define const" run2-0.4.0-1/build/config.h
> 152:#define const /**/
> 
> From the config.log:
> 
> configure:12737: checking for an ANSI C-conforming const
> configure:12802: gcc -c -Wall -Werror  conftest.c >&5
> cc1: warnings being treated as errors
> conftest.c: In function 'main':
> conftest.c:69:10: error: 't' is used uninitialized in this function
> conftest.c:85:23: error: 'b' may be used uninitialized in this function

Looks like a possible bug in autoconf, which is where the definition of
AC_C_CONST comes from -- or they might define this as PIBKAC (see
below).  The test really ought to be -Wall -Werror friendly, but that's
up to the autoconf guys.

Here's a simple test case:

configure.ac
AC_INIT([test])
AC_CONFIG_SRCDIR([configure.ac])
AC_C_CONST

$ autoconf
$ ./configure
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.exe
checking for suffix of executables... .exe
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for an ANSI C-conforming const... yes


$ ./configure CFLAGS="-Wall -Werror"
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.exe
checking for suffix of executables... .exe
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for an ANSI C-conforming const... yes

Hmm...that works fine.  What about:

$ ./configure CC="gcc -Wall -Werror"
checking for gcc... gcc -Wall -Werror
checking whether the C compiler works... yes
checking for C compiler default output file name... a.exe
checking for suffix of executables... .exe
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc -Wall -Werror accepts -g... yes
checking for gcc -Wall -Werror option to accept ISO C89... none needed
checking for an ANSI C-conforming const... no


A-ha!

Don't set -Werror as part of $CC, set it in $CFLAGS instead.

--
Chuck

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -