public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Charles Wilson <cygwin@cwilson.fastmail.fm>
To: cygwin@cygwin.com
Subject: Re: Error building run2 from source package in win7
Date: Tue, 24 May 2011 21:10:00 -0000	[thread overview]
Message-ID: <4DDC1ECD.8030609@cwilson.fastmail.fm> (raw)
In-Reply-To: <20110524195347.GB11571@jethro.local.lan>

On 5/24/2011 3:53 PM, David Sastre wrote:
> On Tue, May 24, 2011 at 02:59:11PM -0400, Charles Wilson wrote:
>> A-ha!
>>
>> Don't set -Werror as part of $CC, set it in $CFLAGS instead.
> 
> Which is what is defined in the *.cygport's src_compile func:
> 
> src_compile() {
>         cd ${S}
>         cygautoreconf
>         cd ${B}
>         cygconf CFLAGS="-Wall -Werror"
>         cygmake
> }
> 
> And I'm doing nothing but running 'cygport *.cygport all'.

Well, Eric is the real expert, and he says don't set the warning flags
until the cygmake line, so that's first.  However, I assume the
incantation above worked in the past for the original author of the
.cygport(5) file, so why's it breaking for you?

Second, why does the STC below not work for you, when it worked for me?

> for the same reasons (config.log):
> 
> configure:2563: gcc -c -Wall -Werror  conftest.c >&5
> cc1: warnings being treated as errors
> conftest.c: In function 'main':
> conftest.c:38:10: error: 't' is used uninitialized in this function
> conftest.c:54:23: error: 'b' may be used uninitialized in this
> function
> configure:2563: $? = 1

Well, looking at my config.log, I too have:

configure:2498: checking for an ANSI C-conforming const
configure:2563: gcc -c -Wall -Werror  conftest.c >&5
                       ^^^^^^^^^^^^^
configure:2563: $? = 0
configure:2570: result: yes

but we already know that this conftest.c is not -Wall -Werror clean --
or, at least, that YOUR conftest.c is not clean.

Digging deeper in my configure, I find that the test uses the shell
function ac_fn_c_try_compile(), and that shell function has an
interesting bit of code:

1340      test -z "$ac_c_werror_flag" ||
1341      test ! -s conftest.err
1342        } && test -s conftest.$ac_objext; then :
1343   ac_retval=0

Hmmm...it's checking something to do with a Werror flag!  Maybe there's
a workaround, but (a) is only activated if the -Werror is in CFLAGS, not
CC -- otherwise *I* would have passed the STC with CC='gcc -Wall
-Werror' but I didn't, and (b) its only present in specific (newer?)
versions of autoconf, and you and I are using different versions.

Here's the first 3 lines of my configure script:

   1 #! /bin/sh
   2 # Guess values for system-dependent variables and create Makefiles.
   3 # Generated by GNU Autoconf 2.68.

What's yours say?

--
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

  reply	other threads:[~2011-05-24 21:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-23 17:18 David Sastre
2011-05-23 17:22 ` Eric Blake
2011-05-23 18:34   ` Charles Wilson
2011-05-24 18:38     ` David Sastre
2011-05-24 18:48       ` Eric Blake
2011-05-24 18:59       ` Charles Wilson
2011-05-24 19:54         ` David Sastre
2011-05-24 21:10           ` Charles Wilson [this message]
2011-05-25 10:34             ` David Sastre

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4DDC1ECD.8030609@cwilson.fastmail.fm \
    --to=cygwin@cwilson.fastmail.fm \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).