From: Eric Blake <eblake@redhat.com>
To: cygwin@cygwin.com
Subject: Re: Error building run2 from source package in win7
Date: Tue, 24 May 2011 18:48:00 -0000 [thread overview]
Message-ID: <4DDBFD4F.1010907@redhat.com> (raw)
In-Reply-To: <20110524183824.GA11571@jethro.local.lan>
[-- Attachment #1: Type: text/plain, Size: 1091 bytes --]
On 05/24/2011 12:38 PM, David Sastre wrote:
> From the config.log:
>
> configure:12737: checking for an ANSI C-conforming const
> configure:12802: gcc -c -Wall -Werror conftest.c >&5
There's your problem.
Autoconf-generated configure scripts do _NOT_ support -Werror; it is too
problematic to ever guarantee that all possible warnings from all
possible gcc versions will always be silenced.
It is permissible to configure without -Werror, and add it later via
'make CFLAGS="-Werror ..."', once configure has found correct results.
But by injecting -Werror too soon into the process, you've made
configure guess a wrong result:
> 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
...
> configure:12809: result: no
with disastrous consequences on the rest of the project compilation.
--
Eric Blake eblake@redhat.com +1-801-349-2682
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 619 bytes --]
next prev parent reply other threads:[~2011-05-24 18:48 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 [this message]
2011-05-24 18:59 ` Charles Wilson
2011-05-24 19:54 ` David Sastre
2011-05-24 21:10 ` Charles Wilson
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=4DDBFD4F.1010907@redhat.com \
--to=eblake@redhat.com \
--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).