public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Eliot Moss <moss@cs.umass.edu>
To: Yeo Kai Wei <yeokaiwei@hotmail.com>, gs-cygwin.com@gluelogic.com
Cc: cygwin@cygwin.com
Subject: Re: [FEEDBACK] Issue with fd_set, FD_ZERO, FD_SET, FD_SETSIZE : Cygwin
Date: Tue, 7 Feb 2023 15:46:32 +1100	[thread overview]
Message-ID: <72efd3b6-e7ab-d45d-d153-4fe410e2d7ab@cs.umass.edu> (raw)
In-Reply-To: <SA1PR05MB9907D0E15F222D4D73A96F88A4DB9@SA1PR05MB9907.namprd05.prod.outlook.com>

On 2/7/2023 3:28 PM, Yeo Kai Wei wrote:
> 
> On 7/2/2023 9:54 am, Eliot Moss wrote:
>> On 2/7/2023 11:34 AM, Yeo Kai Wei wrote:
>>>
>>> On 7/2/2023 7:27 am, Eliot Moss wrote:
>>>> On 2/7/2023 10:03 AM, Yeo Kai Wei via Cygwin wrote:
>>>>>
>>>>> On 7/2/2023 4:59 am, gs-cygwin.com@gluelogic.com wrote:
>>>>>> On Tue, Feb 07, 2023 at 04:33:53AM +0800, Yeo Kai Wei wrote:
>>>>
>>>>> I updated Cygwin to 3.4.5-1.x86_64.
>>>>>
>>>>> $ uname -a
>>>>> CYGWIN_NT-10.0-19045 DESKTOP-P3E71RB 3.4.5-1.x86_64 2023-01-19 19:09 UTC x86_64 Cygwin
>>>>>
>>>>>
>>>>> However, the same problem occurs.
>>>>>
>>>>> Cygwn-devel doesn't seem to work.
>>>>>
>>>>> $ gcc -o selectStdIn selectStdIn.c
>>>>> selectStdIn.c:9:10: fatal error: sys/select.h: No such file or directory
>>>>>   #include <sys/select.h>
>>>>>            ^~~~~~~~~~~~~~
>>>>> compilation terminated.
>>>>
>>>> Well, on my system cygcheck -f /usr/include/sys/select.h clearly says
>>>> that the file came from cygwin-devel-3.4.3-1.  Maybe you misspelled
>>>> cygwin-devel ?  You do have to select the package explicitly, too.
>>>>
>>>> EM
>>>
>>>
>>> Hi Eliot,
>>>
>>> I just reinstalled Cygwin but I'm unsure of what I missed.
>>>
>>> I did "cygcheck -f /usr/include/sys/select.h" and it seems to tell me that I do have 
>>> cygwin-devel-3.4.5-1
>>>
>>> Did I miss a step?
>>
>> What gcc are you running?  Maybe not cygwin's?
>>
>> EM
> 
> 
> Hi Eliot,
> 
> I think I'm running MinGW's gcc.
> 
> I typed in "gcc --version" and this is what Cygwin returned.
> 
> $ gcc --version
> gcc.exe (x86_64-posix-seh-rev0, Built by MinGW-W64 project) 8.1.0
> Copyright (C) 2018 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions. There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> 
> What should I do next?

Install the relevant gcc and program building packages.
But I think you're reaching the limit of the handholding
the community may be prepared to offer ...

Also, you never said what you're *really* trying to
accomplish.

EM

  reply	other threads:[~2023-02-07  4:46 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 [this message]
2023-02-07  5:21                   ` Yeo Kai Wei
2023-02-07  5:51                     ` Eliot Moss
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=72efd3b6-e7ab-d45d-d153-4fe410e2d7ab@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).