From: Marco Atzeri <marco.atzeri@gmail.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: ushort definition
Date: Mon, 09 Jan 2017 16:48:00 -0000 [thread overview]
Message-ID: <9d119899-88ca-c530-c1b4-1a5613dc6daa@gmail.com> (raw)
While building latest gdal
the following bloc of
/usr/include/sys/types.h
-----------------------------------------------------------------------
#if __MISC_VISIBLE
typedef unsigned short ushort; /* System V compatibility */
typedef unsigned int uint; /* System V compatibility */
typedef unsigned long ulong; /* System V compatibility */
#endif
-------------------------------------------------------------------------
seems to cause a puzzling recursive definition
(as reported by g++ -C -E)
$ grep "System V" ../o/.libs/jpeg2000_vsil_io.E
typedef unsigned short unsigned short; /* System V compatibility */
typedef unsigned int unsigned int; /* System V compatibility */
typedef unsigned long unsigned long; /* System V compatibility */
* from System V, which stupidly took internal interface macros and
however I don't see how the definition is read two times
or where ushort was previoulsy defined.
grep "ushort" ../o/.libs/jpeg2000_vsil_io.E
<empty>
What I am missing ?
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
next reply other threads:[~2017-01-09 16:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-09 16:48 Marco Atzeri [this message]
2017-01-09 16:59 ` Corinna Vinschen
2017-01-09 17:48 ` Marco Atzeri
2017-01-09 18:02 ` Hans-Bernhard Bröker
2017-01-09 19:47 ` Marco Atzeri
2017-01-09 22:31 ` Hans-Bernhard Bröker
2017-01-09 23:05 ` Marco Atzeri
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=9d119899-88ca-c530-c1b4-1a5613dc6daa@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).