From: Lisa Anthony <lanthony@cs.cmu.edu>
To: gcc@gcc.gnu.org, cygwin@cygwin.com
Subject: question about cygwin C++ sockets
Date: Thu, 19 Jun 2008 16:54:00 -0000 [thread overview]
Message-ID: <485A8725.9030202@cs.cmu.edu> (raw)
I have an application I've been working on for a couple years now that
uses this C++ socket library: http://www.alhem.net/Sockets/index.html.
I recently decided to try upgrading the sockets library I had to the
latest one, and have been having conflict problems with building my app
with the new library, which now depends on the winsock32 library. I am
unable to build my app now, because cygwin's implementation of the
gethostname function conflicts with winsock's:
/usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../../include/w32api/winsock2.h:635:
error: declaration of C function `int gethostname(char*, int)' conflicts
with /usr/include/sys/unistd.h:206: error: previous declaration `int
gethostname(char*, size_t)' here
I found this message, and was wondering if the OP's suggestion has been
addressed or included in later versions of cygwin gcc? (I'm guessing no.)
http://gcc.gnu.org/ml/gcc/2006-05/msg00627.html
It was quite a while ago, but I'm having the same problem as the OP
describes, with recent releases of cygwin and gcc (the version included
in the current cygwin distro).
Compiling with the -mno-cygwin flag (recommended by the socket library
author) gives me different errors (can't find pthread.h).
Any input would be appreciated,
Thanks,
*Lisa
--
*Lisa Anthony
PhD Candidate
http://www.cs.cmu.edu/~lanthony/
Human-Computer Interaction Institute
Carnegie Mellon University, Pittsburgh, PA
"The best way to predict the future is to invent it."
Alan Kay
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
reply other threads:[~2008-06-19 16:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=485A8725.9030202@cs.cmu.edu \
--to=lanthony@cs.cmu.edu \
--cc=cygwin@cygwin.com \
--cc=gcc@gcc.gnu.org \
/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).