From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9100 invoked by alias); 20 Jun 2012 20:40:25 -0000 Received: (qmail 9082 invoked by uid 22791); 20 Jun 2012 20:40:23 -0000 X-SWARE-Spam-Status: No, hits=-1.5 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE,RCVD_IN_SORBS_WEB,SPF_HELO_PASS,TW_YG X-Spam-Check-By: sourceware.org Received: from mout.perfora.net (HELO mout.perfora.net) (74.208.4.195) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 20 Jun 2012 20:40:06 +0000 Received: from JamesJPC (75-146-80-177-Chattanooga.hfc.comcastbusiness.net [75.146.80.177]) by mrelay.perfora.net (node=mrus4) with ESMTP (Nemesis) id 0MFtnC-1SdXfu1nlO-00ERsB; Wed, 20 Jun 2012 16:40:05 -0400 From: "James Johnston" To: References: In-Reply-To: Subject: RE: stdout not visible on some programs after upgrading from to 1.7.11-1 to 1.7.15-1 Date: Wed, 20 Jun 2012 20:40:00 -0000 Message-ID: <010201cd4f24$d2eeba50$78cc2ef0$@motionview3d.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2012-06/txt/msg00385.txt.bz2 > -----Original Message----- > Sent: Wednesday, June 20, 2012 16:27 > Subject: stdout not visible on some programs after upgrading from to 1.7.11- > 1 to 1.7.15-1 > > Hello, > > I use cygwin on a windows 7 machine to automate a Visual Studio 10 build > from the command line. To do this, I invoke MSBuild.exe with a wrapper > script called msbuild.sh (see below). Under cygwin 1.7.11-1, the stdout from > msbuild.exe appears on the console where I invoke msbuild.sh as expected. > But after a recent upgrade to 1.7.15-1, the stdout stops appearing. By > inspecting the running processes in the windows task manager, I see that > msbuild.exe is launching the compiler, etc. Notably, if I replace the > invocation of msbuild.exe with another program (e.g., dir), I do see the > expected stdout. > Further, if I execute the relevant commands in the native cmd shell, I do see > the msbuild.exe output. I considered tracking down the specific package > that lead to this regression, but I didn't find a mirror with the older packages. > Below I've pasted the output of cygcheck -c for the working and failing > systems. Can somebody advise me on a sensible next steps to recovering > the stdout of msbuild.exe? > > Please CC me in responses. > > Thanks, > Brian Try both of the following: 1. Update to latest development snapshot, should resolve the bug you are primarily observing. 2. Set the CYGWIN environment variable to pipe_byte. Cygwin now uses message pipes by default, which are not compatible with .NET Framework and Visual C++ runtimes (not currently documented anywhere in Cygwin or MS documentation). -- 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