From: "Lloyd Wood via cygwin" <cygwin@cygwin.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: configure fails on checking ino_t
Date: Wed, 07 Jun 2017 06:21:00 -0000 [thread overview]
Message-ID: <310357481.6222896.1496816466443@mail.yahoo.com> (raw)
In-Reply-To: <310357481.6222896.1496816466443.ref@mail.yahoo.com>
download geomview 1.9.5 from http://www.geomview.org
this used to build on cygwin 32-bit. Did so for a number of years. Now, it doesn't,
because something changed.
$ tar xvfz geomview-1.9.5.tar.gz
$ cd geomview-1.9.5
./configure
[..]
checking for dev_t... yes
checking for ino_t... yes
checking for time_t... yes
checking size of dev_t... 4
checking size of ino_t... configure: error: in `/home/ellowoo/savi/geomview-1.9.5':
configure: error: cannot compute sizeof (ino_t)
See `config.log' for more details
$ tail config.log
[..]
#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
Okay, so what changed in Cygwin?
(No, Mario, this is not an antivirus thing...)
thanks
Lloyd Wood
http://savi.sf.net/
--
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
next parent reply other threads:[~2017-06-07 6:21 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 [this message]
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
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=310357481.6222896.1496816466443@mail.yahoo.com \
--to=cygwin@cygwin.com \
--cc=lloyd.wood@yahoo.co.uk \
/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).