public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Yeo Kai Wei <yeokaiwei@hotmail.com>
To: 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 07:03:23 +0800	[thread overview]
Message-ID: <SA1PR05MB99072D6C9EAFB28AFFDD6D72A4DA9@SA1PR05MB9907.namprd05.prod.outlook.com> (raw)
In-Reply-To: <Y+FqT9AbejDHsg7h@xps13>


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:
>> Hi All,
>>
>> Thanks for the help.
>>
>> I tried adding "#include <sys/select.h>".
>>
>> However, this is the error message that was returned to me.
>>
>> $ gcc -o selectStdIn selectStdIn.c
>> selectStdIn.c:9:10: fatal error: sys/select.h: No such file or directory
>>   #include <sys/select.h>
>>
>> Thank you.
>>
>> On 7/2/2023 4:30 am, gs-cygwin.com@gluelogic.com wrote:
>>> On Tue, Feb 07, 2023 at 04:25:22AM +0800, Yeo Kai Wei via Cygwin wrote:
>>>> Hi,
>>>>
>>>> I would like to report an issue with Cygwin 3.4.2 on Windows.
>>>>
>>>> It doesn't seem to be able to work with  fd_set, FD_ZERO, FD_SET, FD_SETSIZE
>>>> macros.
>>>>
>>>> The code is in italics. The filename was selectStdIn.c. The terminal command
>>>> used was "gcc -o selectStdIn selectStdIn.c"
>>>>
>>>> Thank you.
>>>>
>>>> /
>>>> /
>>>>
>>>> /CODE
>>>> /
>>>>
>>>> /#include <stdio.h>//
>>>> //#include <stdlib.h>//
>>>> //#include <sys/time.h>//
>>>> //#include <unistd.h>//
>>>> / /
>>>> //void main()//
>>>> //{//
>>>> //    fd_set fds; //set of file descriptors//
>>>> / /
>>>> //    struct timeval tv;//
>>>> / /
>>>> //    int flag;//
>>>> / /
>>>> //    char byte;//
>>>> / /
>>>> //    FD_ZERO(&fds);//
>>>> / /
>>>> //    FD_SET(0, &fds);//
>>>> / /
>>>> //    tv.tv_sec = 5;//
>>>> / /
>>>> //    tv.tv_usec = 0;//
>>>> / /
>>>> //    flag = select(FD_SETSIZE, //
>>>> //            &fds,//
>>>> //            NULL,//
>>>> //            NULL,//
>>>> //            &tv);//
>>>> / /
>>>> //    if(-1 == flag)//
>>>> //        perror("select error");//
>>>> //    else if(flag)//
>>>> //    {//
>>>> //        read(0,&byte,1);//
>>>> / /
>>>> //        puts("data read");//
>>>> //    }//
>>>> / /
>>>> //    if(flag)//
>>>> //        printf("The byte value is %c\n", byte);//
>>>> ////
>>>> //}/
>>>>
>>>>
>>>> TERMINAL COMMANDS
>>>>
>>>> $ gcc -o selectStdIn selectStdIn.c
>>>> selectStdIn.c: In function 'main':
>>>> selectStdIn.c:8:2: error: unknown type name 'fd_set'; did you mean 'fpos_t'?
>>>>     fd_set fds; //set of file descriptors
>>>>     ^~~~~~
>>>>     fpos_t
>>>> selectStdIn.c:16:2: warning: implicit declaration of function 'FD_ZERO'
>>>> [-Wimpli
>>>> cit-function-declaration]
>>>>     FD_ZERO(&fds);
>>>>     ^~~~~~~
>>>> selectStdIn.c:18:2: warning: implicit declaration of function 'FD_SET'
>>>> [-Wimplic
>>>> it-function-declaration]
>>>>     FD_SET(0, &fds);
>>>>     ^~~~~~
>>>> selectStdIn.c:24:9: warning: implicit declaration of function 'select'; did
>>>> you
>>>> mean 'sleep'? [-Wimplicit-function-declaration]
>>>>     flag = select(FD_SETSIZE,
>>>>            ^~~~~~
>>>>            sleep
>>>> selectStdIn.c:24:16: error: 'FD_SETSIZE' undeclared (first use in this
>>>> function)
>>>>     flag = select(FD_SETSIZE,
>>>>                   ^~~~~~~~~~
>>>> selectStdIn.c:24:16: note: each undeclared identifier is reported only once
>>>> for
>>>> each function it appears in
>>> $ man select
>>>
>>> #include <sys/select.h>
> Please post at bottom of messages on this mailing list.
>
> You need to install the cygwin-devel package to get <sys/select.h>
>
> Cheers, Glenn

Hi All,

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.


  parent reply	other threads:[~2023-02-06 23:03 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 [this message]
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
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=SA1PR05MB99072D6C9EAFB28AFFDD6D72A4DA9@SA1PR05MB9907.namprd05.prod.outlook.com \
    --to=yeokaiwei@hotmail.com \
    --cc=cygwin@cygwin.com \
    --cc=gs-cygwin.com@gluelogic.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).