From: Michael Eager <eager@mvista.com>
To: Cygwin Mailing List <cygwin@cygwin.com>
Subject: MS_types and addr_t name polution
Date: Wed, 11 Dec 2002 20:13:00 -0000 [thread overview]
Message-ID: <3DF7FE42.29FCA9C1@mvista.com> (raw)
I'm porting a small program to Cygwin. One of the typedefs
in the program is for a symbol named addr_t. Since this is
defined in /usr/include/sys/types.h, there is a redefinition
conflict.
This (and a number of other symbols) are defined when __MS_types_
is defined, which, in turn, is defined whenever __CYGWIN__, _WIN32
or __MSDOS__ is defined.
I don't see any use of addr_t in /usr/include. Is there a reason
for defining addr_t and the other symbols?
--
Michael Eager eager@mvista.com 408-328-8426
MontaVista Software, Inc. 1237 E. Arques Ave., Sunnyvale, CA 94085
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next reply other threads:[~2002-12-12 3:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-11 20:13 Michael Eager [this message]
2002-12-12 0:12 Elfyn McBratney
2002-12-12 14:58 ` Michael Eager
2002-12-12 16:40 ` Christopher Faylor
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=3DF7FE42.29FCA9C1@mvista.com \
--to=eager@mvista.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).