From: Mark Geisert <mark@maxrnd.com>
To: cygwin@cygwin.com
Subject: Re: Patch request to qt 5.9.4
Date: Fri, 15 Mar 2019 08:06:00 -0000 [thread overview]
Message-ID: <17710c05-3ccc-b8de-6b8b-db022c1f1ce3@maxrnd.com> (raw)
In-Reply-To: <Pine.BSF.4.63.1903130118170.46302@m0.truegem.net>
Mark Geisert wrote:
> I believe I've found the root cause of this issue of outbound connect on a
> non-blocking socket not working under Cygwin.
[...]
Hi Tatsuro,
This Qt issue should be reported to their developers. Do you have experience
opening a ticket with them? If so, please do so and let me know the ticket/bug
number. I will participate in discussion there. I could also open a ticket
myself if you prefer that I do it.
It seems to me that we should continue to apply your one-line patch that turns
off O_NONBLOCK at that one Qt location, as a workaround for this Qt problem on
Cygwin. When the Qt devs fix the root cause and release a new Qt containing the
fix, we can then remove our local patch.
..mark
Yaakov: Does this all sound reasonable to you?
--
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
next prev parent reply other threads:[~2019-03-15 8:06 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 ` Patch request to qt 5.9.4 (Re: [ANNOUNCEMENT] Qt 5.9.4) 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
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 [this message]
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=17710c05-3ccc-b8de-6b8b-db022c1f1ce3@maxrnd.com \
--to=mark@maxrnd.com \
--cc=cygwin@cygwin.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).