public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: cygwin@cygwin.com
Subject: Re: configure fails on checking ino_t
Date: Wed, 07 Jun 2017 22:19:00 -0000	[thread overview]
Message-ID: <6b85944b-bb04-0a6a-2a7d-1dcc7bc2fc1f@redhat.com> (raw)
In-Reply-To: <1462809442.7598271.1496873467329@mail.yahoo.com>


[-- Attachment #1.1: Type: text/plain, Size: 1191 bytes --]

On 06/07/2017 05:11 PM, Lloyd Wood via cygwin wrote:

Please don't top-post on technical lists.

> Aha! just slightly later in config.log:
> 
> configure:17957: checking for ino_t 
> configure:17957: gcc -c -g -O2  conftest.c >&5 
> configure:17957: $? = 0 
> configure:17957: gcc -c -g -O2  conftest.c >&5 
> conftest.c: In function 'main': 
> conftest.c:94:20: error: expected expression before ')' token 
> if (sizeof ((ino_t))) 
> ^ 

This _particular_ failure is expected (you aren't showing enough of the
config.log output).  Remember, to determine if something is a type vs.
an expression, autoconf performs TWO compilation tests, and relies on
the fact that sizeof(expr) and sizeof((expr)) both compile, but
sizeof(type) compiles while sizeof((type)) must fail.  The back-to-back
compilation is necessary to ensure that something being probed for is a
type name rather than an arbitray expression.

So just because _some_ tests fail (as expected) does not mean that this
particular failure is where configure is messing up.


-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3266
Virtualization:  qemu.org | libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]

  reply	other threads:[~2017-06-07 22:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <310357481.6222896.1496816466443.ref@mail.yahoo.com>
2017-06-07  6:21 ` Lloyd Wood via cygwin
2017-06-07  9:35   ` Corinna Vinschen
2017-06-07 19:10   ` Csaba Raduly
2017-06-07 20:37     ` Lloyd Wood via cygwin
2017-06-07 22:11       ` Lloyd Wood via cygwin
2017-06-07 22:19         ` Eric Blake [this message]
2017-06-08  8:27           ` Csaba Raduly
2017-06-08  2:44       ` Brian Inglis
2017-06-09 20:38   ` Ken Brown
2017-06-09 23:22     ` Lloyd Wood via cygwin
2017-06-10  1:53       ` Ken Brown
2017-06-11  0:22         ` Lloyd Wood via cygwin

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=6b85944b-bb04-0a6a-2a7d-1dcc7bc2fc1f@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).