public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Tatsuro MATSUOKA <tmacchant2@yahoo.co.jp>
To: Achim Gratz <Stromeko@nexgo.de>,  <cygwin@cygwin.com>
Subject: Re: Patch request to qt 5.9.4 (Re: [ANNOUNCEMENT] Qt 5.9.4)
Date: Wed, 06 Mar 2019 01:10:00 -0000	[thread overview]
Message-ID: <1869437449.2276597.1551834619821.JavaMail.yahoo@mail.yahoo.co.jp> (raw)
In-Reply-To: <648344595.103002.1551831017801.JavaMail.yahoo@mail.yahoo.co.jp>

>>  From: Achim Gratz

>>  To: cygwin
>>  Cc: 
>>  Date: 2019/3/6, Wed 04:24
>>  Subject: Re: Patch request to qt 5.9.4 (Re: [ANNOUNCEMENT] Qt 5.9.4)
>> 
>> T atsuro MATSUOKA writes:
>>>   I contacted with Enrico who tells me the patch that I have shown.
>> 
>>  Yes, but that monkeys around the real problem.  What Yaakov is telling
>>  you is that there are two options and we don't know yet which one we
>>  have to deal with.
>> 
>>  If O_NONBLOCK is needed, but does not work correctly under Cygwin, then
>>  that's a bug in Cygwin.  For this case, Corinna asks you to create an
>>  STC that demonstrates the bug so it can be triaged without having to
>>  work with something as complex as the Qt terminal in Cygwin.
>> 
>>  If on the other hand O_NONBLOCK is in fact not needed and just shows
>>  different behaviour on different systems without a bug in the
>>  implementation being present, then upstream should remove that argument.
>> 
>> 
>>  Regards,
>>  Achim.
> 
> Seeing ML archive that Enrico indicated,
> 
> Re: select() and named pipes
> 
> #include <stdio.h>
> #include <stdlib.h>
> #include <errno.h>
> #include <sys/select.h>
> #include <sys/types.h>
> #include <sys/stat.h>
> #include <fcntl.h>
> #include <unistd.h>
> 
> #define FIFONAME "/tmp/pipe"
> 
> int main(void)
> {
>     int fd;
>     int nsel;
>     fd_set readfds;
>     FD_ZERO(&readfds);
> 
>     if (mkfifo(FIFONAME, 0600) < 0) {
>         perror("mkfifo");
>         exit(1);
>     }
> 
>     fd = open(FIFONAME, O_RDONLY | O_NONBLOCK);
> 
>     if (fd < 0) {
>         perror("open");
>         remove(FIFONAME);
>         exit(2);
>     }
> 
>     FD_SET(fd, &readfds);
>     do {
>         nsel = select(fd + 1, &readfds, 0, 0, 0);
>     } while (nsel == -1 && (errno == EINTR || errno == EAGAIN));
> 
>     if (nsel == -1) {
>         perror("select");
>         exit(3);
>     }
> 
>     if (FD_ISSET(fd, &readfds)) {
>         char buf[100];
>         int status;
>         int count = 0;
>         printf("%d: ", ++count);
>         while ((status = read(fd, buf, sizeof(buf) - 1))) {
>             if (status > 0) {
>                 buf[status] = '\0';
>                 printf("%s", buf);
>             } else if (errno == EAGAIN) {
>                     printf("\n%d: ", ++count);
>             } else {
>                 perror("read");
>                 break;
>             }
>         }
>     }
> 
>     close(fd);
>     remove(FIFONAME);
>     return 0;
> }
> 
> 
> 
> As you wrote this is a issue of Cygwin issue.
> But As long as O_NONBLOCK does not work on Cygwin, Enrico's workaround can 
> be attached for qt.

Apart from Qt maintainer accepts Enrico's patch, I will raise O_NONBLOCK issue by another post.

Tatsuro


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2019-03-06  1:10 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1439412702.1866573.1551653028041.JavaMail.yahoo.ref@mail.yahoo.co.jp>
2019-03-03 22:43 ` Tatsuro MATSUOKA
2019-03-04 16:32   ` Yaakov Selkowitz
2019-03-04 22:29     ` Tatsuro MATSUOKA
2019-03-05 12:57     ` Tatsuro MATSUOKA
2019-03-05 19:24       ` Achim Gratz
2019-03-05 23:58         ` Tatsuro MATSUOKA
2019-03-06  0:10         ` Tatsuro MATSUOKA
2019-03-06  1:10           ` Tatsuro MATSUOKA [this message]
2019-03-06  1:55             ` Tatsuro MATSUOKA
2019-03-06  2:25               ` Tatsuro MATSUOKA
2019-03-11  0:28     ` Tatsuro MATSUOKA
2019-03-11  0:50       ` Andrey Repin
2019-03-11  0:53       ` Yaakov Selkowitz
2019-03-11  3:33         ` Tatsuro MATSUOKA
2019-03-11  7:21           ` Mark Geisert
2019-03-11  7:56             ` Tatsuro MATSUOKA
2019-03-12  4:21               ` Mark Geisert
2019-03-12  6:51                 ` Tatsuro MATSUOKA
2019-03-12  8:04                   ` Patch request to qt 5.9.4 Mark Geisert
2019-03-12  8:26                     ` Tatsuro MATSUOKA
2019-03-12 19:37                       ` Achim Gratz
2019-03-12 23:22                       ` Tatsuro MATSUOKA
2019-03-13  1:12                         ` Mark Geisert
2019-03-13  4:27                           ` Tatsuro MATSUOKA
2019-03-13  8:33                             ` Mark Geisert
2019-03-15  8:06                               ` Mark Geisert
2019-03-15  9:40                                 ` Tatsuro MATSUOKA
2019-03-16  0:41                                   ` Tatsuro MATSUOKA
2019-03-12 19:34                     ` Achim Gratz
2019-03-11  9:45             ` Patch request to qt 5.9.4 (Re: [ANNOUNCEMENT] Qt 5.9.4) Corinna Vinschen
2019-03-12  4:16               ` Mark Geisert

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=1869437449.2276597.1551834619821.JavaMail.yahoo@mail.yahoo.co.jp \
    --to=tmacchant2@yahoo.co.jp \
    --cc=Stromeko@nexgo.de \
    --cc=cygwin@cygwin.com \
    --cc=matsuoka@nuce.nagoya-u.ac.jp \
    /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).