From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: ino_t and d_ino now a thing again?
Date: Wed, 31 May 2017 06:56:00 -0000 [thread overview]
Message-ID: <eb19f806-1059-ff4e-6fd5-8c93447469e0@gmail.com> (raw)
In-Reply-To: <71025238.6174642.1496192540488@mail.yahoo.com>
On 31/05/2017 03:02, Lloyd Wood via cygwin wrote:
> Hi,
>
> on attempting to build Geomview 1.9.5 on current updated
> Cygwin, configure fails oddly:
>
> ./configure
> [..]
> checking for time_t... yes
> checking size of dev_t... 4
> checking size of ino_t... configure: error: in `/home/lloyd/savi/geomview-1.9.5':
> configure: error: cannot compute sizeof (ino_t)
> See `config.log' for more details
>
> lloyd@box ~/savi/geomview-1.9.5
> $ tail config.log
> #define HAVE__BOOL 1
> #define HAVE_STDBOOL_H 1
> #define TIME_WITH_SYS_TIME 1
> #define HAVE_M_PI 1
> #define HAVE_DEV_T 1
> #define HAVE_INO_T 1
> #define HAVE_TIME_T 1
> #define SIZEOF_DEV_T 4
>
> configure: exit 77
>
>
> If HAVE_INO_T is 1, getting sizeof should be a non-problem.
check the exact reason of the failed test in the config.log .
I have similar issue and it is due to the antivirus locking the test
file too long.
>
> Is this a reoccurrence of the 2006 d_ino problems that were an issue for Cygwin
> 1.5.19, and discussed with Eric Blake?
>
> thanks and regards
>
> Lloyd Wood
Regards
Marco
--
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
prev parent reply other threads:[~2017-05-31 5:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <71025238.6174642.1496192540488.ref@mail.yahoo.com>
2017-05-31 2:30 ` Lloyd Wood via cygwin
2017-05-31 6:56 ` Marco Atzeri [this message]
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=eb19f806-1059-ff4e-6fd5-8c93447469e0@gmail.com \
--to=marco.atzeri@gmail.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).