From: Steve Kenton <skenton@ou.edu>
To: cygwin@sourceware.cygnus.com
Subject: sys/socket.h problem
Date: Fri, 22 Sep 2000 09:21:00 -0000 [thread overview]
Message-ID: <39CB86D6.D253A3BA@ou.edu> (raw)
I think there is a minor problem in sys/socket.h
The 3rd parameter to accept() is normally declared to be of type socklen_t which
ultimately
ought to cast to some unsigned type rather than signed int. As is, gcc
complains about the
sign changing and refused to build some socket code from a previously working
package. Changing
the definition from int to uint works around my problem, but it makes we wonder
how all of the
network application included in cygwin were built.
Steve Kenton
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next reply other threads:[~2000-09-22 9:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-22 9:21 Steve Kenton [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-11-30 13:12 Mark Schoenberg
1999-11-30 13:39 ` Cygnus - Admin
1999-11-30 23:39 ` Cygnus - Admin
1999-11-30 13:56 ` Corinna Vinschen
1999-11-30 23:39 ` Corinna Vinschen
1999-11-30 23:39 ` Mark Schoenberg
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=39CB86D6.D253A3BA@ou.edu \
--to=skenton@ou.edu \
--cc=cygwin@sourceware.cygnus.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).