DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:reply-to:to:message-id:in-reply-to
	:references:subject:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=CRZwtTjRTjD3S46V
	Mu4o8iReq40xl8+/Ov/IkyMckJ0YpPYLz4+MoglXB8S4A/x3MfmuaCYppjQdYSQl
	eeX2OyPeIa4rFCH/wwd4JSz2/4oDrIgyMeb/pTsagbBq7I3If7jIM6/BUJ+iZZvh
	4SKbS5GRQwoA8jB1IEuq7vafYfY=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=yj20110701; d=yahoo.co.jp;	h=Date:From:Reply-To:Message-ID:In-Reply-To:References:MIME-Version:Content-Type:Content-Transfer-Encoding;	b=X4Ys7B+IezWgxyMNBxIr+CH/byzVQq5si9T5hpDBHAJJWCAIiZgX5Ww2HdicSzke	XheFK1n4xBAy6dXvbo7Eh/HEwJTGvftPx2i0PKE2OGzugk8TRqSH+foVJJR74tej6g3	LXINCbYQ/kUstPNVqJSPtPSM3tMjSrMEjBV94Upc=;
Date: Sat, 16 Mar 2019 09:41:19 +0900 (JST)
From: Tatsuro MATSUOKA <tmacchant2@yahoo.co.jp>
Reply-To: Tatsuro MATSUOKA <matsuoka@nuce.nagoya-u.ac.jp>
To: Mark Geisert <mark@maxrnd.com>, <cygwin@cygwin.com>
Message-ID: <1252985381.1651988.1552696879328.JavaMail.yahoo@mail.yahoo.co.jp>
In-Reply-To: <1216344404.1733525.1552642814407.JavaMail.yahoo@mail.yahoo.co.jp>
References: <1439412702.1866573.1551653028041.JavaMail.yahoo.ref@mail.yahoo.co.jp> <1439412702.1866573.1551653028041.JavaMail.yahoo@mail.yahoo.co.jp> <0faa5fb55a0af4803fcdff786dba8be440355609.camel@cygwin.com> <1346787976.482037.1552451229824.JavaMail.yahoo@mail.yahoo.co.jp> <Pine.BSF.4.63.1903130118170.46302@m0.truegem.net> <17710c05-3ccc-b8de-6b8b-db022c1f1ce3@maxrnd.com> <1216344404.1733525.1552642814407.JavaMail.yahoo@mail.yahoo.co.jp>
Subject: Re: Patch request to qt 5.9.4
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

>>  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?
>>  
> I do not have experience opening a ticket of Qt.
> However, I frequently open bug tickets to gnuplot and GNU Octave.
> 
> I will try it tomorrow and report here about submit of the ticket.

Mark

I created the Qt bug.

https://bugreports.qt.io/browse/QTBUG-74486

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