From: Eliot Moss <moss@cs.umass.edu>
To: Yeo Kai Wei <yeokaiwei@hotmail.com>,
"gs-cygwin.com@gluelogic.com" <gs-cygwin.com@gluelogic.com>
Cc: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: [FEEDBACK] Issue with fd_set, FD_ZERO, FD_SET, FD_SETSIZE : Cygwin
Date: Tue, 7 Feb 2023 16:51:02 +1100 [thread overview]
Message-ID: <84a0058b-057e-e11d-e836-4f3a9bcb83ca@cs.umass.edu> (raw)
In-Reply-To: <SA1PR05MB9907BD8A437F581A1ED7DE3DA4DB9@SA1PR05MB9907.namprd05.prod.outlook.com>
Ok ... assuming the "Modern C" is more or less POSIX based and
does not use things outside the realm of what cygwin supplies,
I think the answer is straightforward:
Make sure you install every program and every library that the
book uses. There's not really such a thing as a "full install"
for Cygwin (and it would huge anyway), so you'll have to figure
out what going through the book demands. Fortunately, you can
somewhat do that as you go, finding packages that need to be
installed.
Best wishes - EM
next prev parent reply other threads:[~2023-02-07 5:51 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 20:25 Yeo Kai Wei
2023-02-06 20:30 ` gs-cygwin.com
2023-02-06 20:33 ` Yeo Kai Wei
2023-02-06 20:59 ` gs-cygwin.com
2023-02-06 22:50 ` Yeo Kai Wei
2023-02-06 23:03 ` Yeo Kai Wei
2023-02-06 23:19 ` gs-cygwin.com
2023-02-06 23:27 ` Eliot Moss
2023-02-06 23:48 ` Yeo Kai Wei
2023-02-06 23:50 ` Eliot Moss
2023-02-06 23:53 ` Yeo Kai Wei
[not found] ` <PH0PR05MB9918F39B0B689DFF52980D11A4DB9@PH0PR05MB9918.namprd05.prod.outlook.com>
2023-02-07 1:53 ` Eliot Moss
2023-02-07 0:34 ` Yeo Kai Wei
2023-02-07 1:54 ` Eliot Moss
2023-02-07 3:15 ` Yeo Kai Wei
2023-02-07 3:56 ` Yeo Kai Wei
2023-02-07 4:44 ` Eliot Moss
2023-02-07 4:28 ` Yeo Kai Wei
2023-02-07 4:46 ` Eliot Moss
2023-02-07 5:21 ` Yeo Kai Wei
2023-02-07 5:51 ` Eliot Moss [this message]
2023-02-07 5:53 ` Brian Inglis
2023-02-07 6:59 ` Yeo Kai Wei
2023-02-07 8:43 ` Hans-Bernhard Bröker
2023-02-06 20:31 ` Eliot Moss
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=84a0058b-057e-e11d-e836-4f3a9bcb83ca@cs.umass.edu \
--to=moss@cs.umass.edu \
--cc=cygwin@cygwin.com \
--cc=gs-cygwin.com@gluelogic.com \
--cc=yeokaiwei@hotmail.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).