X-Recipient:	archive-cygwin AT delorie DOT com
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org D88353858432
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1636618833;
	bh=3/r2rf5Osva6Kf9nmxEucngz45VeZ7WxKe8w6TMtSDI=;
	h=Date:To:Subject:In-Reply-To:References:List-Id:List-Unsubscribe:
	List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:
	From;
	b=PziQXBfSs/dVff1Yz0d2UqSBby9yLt6TE2oECdt4Ys1MUEEIyHGcCRI8P0sG2r+83
	7B2A9oKfgJAMu8BJhyZPddCE3fGNzeD4wn+9ArWPN/Lbz72/ImwU8g23TL6R1k4g22
	jFA/55QWPtH1aHxAH/nbQP9HU1D4FEdfPoR6G2P4=
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.4.1 sourceware.org D9F5C385841D
DKIM-Filter:	OpenDKIM Filter v2.10.3 conssluserg-05.nifty.com 1AB8IdOj003017
X-Nifty-SrcIP:	[110.4.221.123]
Date:	Thu, 11 Nov 2021 17:18:39 +0900
To:	cygwin AT cygwin DOT com
Subject:	Re: Console output broken in version 3.3.x under native ninja
Message-Id:	<20211111171839.34cb325261ae7a6f82923de1@nifty.ne.jp>
In-Reply-To:	<BL3PR08MB7451C16C03ACC04FFE32E812F3939@BL3PR08MB7451.namprd08.prod.outlook.com>
References:	<BL3PR08MB7451C16C03ACC04FFE32E812F3939 AT BL3PR08MB7451 DOT namprd08 DOT prod DOT outlook DOT com>
X-Mailer:	Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32)
Mime-Version:	1.0
X-Spam-Status:	No, score=-6.2 required=5.0 tests=BAYES_00, DKIM_SIGNED,
	DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, NICE_REPLY_A, RCVD_IN_DNSWL_NONE,
	SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.4
X-Spam-Checker-Version:	SpamAssassin 3.4.4 (2020-01-24) on
	server2.sourceware.org
X-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.29
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe:	<https://cygwin.com/mailman/options/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive:	<https://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<https://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From:	Takashi Yano via Cygwin <cygwin AT cygwin DOT com>
Reply-To:	Takashi Yano <takashi DOT yano AT nifty DOT ne DOT jp>
Errors-To:	cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com
Sender:	"Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com>

On Wed, 10 Nov 2021 15:40:37 +0000
"Bresalier, Rob \(Nokia - US/Murray Hill\) wrote:
> Hi:
> 
> This worked fine with Cygwin 3.2.0 but is broken starting with Cygwin 3.3.0, hence I think it is a Cygwin bug and not a ninja bug.
> 
> When running Cygwin applications under Windows native 'ninja.exe' build tool (not the Cygwin packaged one) then the stdout is not emitted to the console starting with Cygwin 3.3.0. It worked fine with Cygwin 3.2.0 and stdout is emitted to the console. If using Cygwin ninja with 3.3.0 it also works. The problem is with Windows native ninja and Cygwin programs with Cygwin version 3.3.0 and later.
> 
> Using Cygwin ninja is not an option for us as a solution. We need to use the Windows native ninja for reasons that I won't go into here.
> 
> To reproduce the issue:
> 
> 1) Download windows native ninja from here: https://github.com/ninja-build/ninja/releases
>    a. Use ninja-win.zip that has the ninja.exe executable
>    b. DO NOT USE the Cygwin version of ninja
> 
> 2) Below is a sample build.ninja file that demonstrates the problem. This sample build.ninja simply causes bash -help to run. Create this build.ninja text file in some directory.
> 
> 3) cd to the directory where you have the build.ninja, and then run the native ninja.exe, you won't see the bash --help output with Cygwin 3.3.0 and later.
>   a. I suggesting using -v option with ninja.exe: "path/to/native/ninja.exe -v"
> 
> 4) If you try it with Cygwin 3.2.0 it works fine you will see the bash --help output.
> 
> 5) If you run c:/cygwin64/bin/bash --help outside of ninja it works fine.
> 
> 6) This happens if you run the native ninja.exe from either a command window or from the Cygwin/minty/bash
> 
> Here is the sample build.ninja to be used to reproduce the problem:
> 
> --------start build.ninja --------------
> rule CUSTOM_COMMAND
>   command = $COMMAND
>   description = $DESC
> 
> build MC5U_BMDCO6_versions.txt: CUSTOM_COMMAND
>   COMMAND = c:/cygwin64/bin/bash --help
>   DESC = Running bash --help
>   restat = 1
> --------end build.ninja --------------
> 
> Thanks for having a look.

Thanks for the report.

I could reproduce your problem and found the cause.

Windows native ninja creates pipe with size zero, which cannot
be handled correctly by current cygwin pipe code (raw_write()).

I will submit a patch for this issue shortly.

-- 
Takashi Yano <takashi DOT yano AT nifty DOT ne DOT jp>

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

- Raw text -