From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29572 invoked by alias); 22 Jun 2012 19:11:45 -0000 Received: (qmail 29554 invoked by uid 22791); 22 Jun 2012 19:11:43 -0000 X-SWARE-Spam-Status: No, hits=-3.0 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,FREEMAIL_FROM,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,TW_YG X-Spam-Check-By: sourceware.org Received: from mail-qc0-f170.google.com (HELO mail-qc0-f170.google.com) (209.85.216.170) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 22 Jun 2012 19:11:27 +0000 Received: by qcmt36 with SMTP id t36so1250514qcm.15 for ; Fri, 22 Jun 2012 12:11:26 -0700 (PDT) MIME-Version: 1.0 Received: by 10.224.58.201 with SMTP id i9mr8438970qah.39.1340392286391; Fri, 22 Jun 2012 12:11:26 -0700 (PDT) Received: by 10.229.85.85 with HTTP; Fri, 22 Jun 2012 12:11:26 -0700 (PDT) In-Reply-To: <010201cd4f24$d2eeba50$78cc2ef0$@motionview3d.com> References: <010201cd4f24$d2eeba50$78cc2ef0$@motionview3d.com> Date: Fri, 22 Jun 2012 19:11:00 -0000 Message-ID: Subject: Re: stdout not visible on some programs after upgrading from to 1.7.11-1 to 1.7.15-1 From: Brian Cavagnolo To: cygwin@cygwin.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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/msg00424.txt.bz2 On Wed, Jun 20, 2012 at 1:39 PM, James Johnston w= rote: >> -----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. =A0To do this, I invoke MSBuild.exe with a wrapper >> script called msbuild.sh (see below). =A0Under cygwin 1.7.11-1, the stdo= ut > 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. =A0By >> inspecting the running processes in the windows task manager, I see that >> msbuild.exe is launching the compiler, etc. =A0Notably, 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. =A0I considered tracking down the specific packa= ge >> 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. =A0Can 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. =A0Update to latest development snapshot, should resolve the bug you a= re > primarily observing. > 2. =A0Set the CYGWIN environment variable to pipe_byte. =A0Cygwin 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). For kicks, I tried 2 by itself. This didn't change the behavior. Next, I tried 1 by itself as described in [1]. This worked. Adding in CYGWIN=3Dpipe_byte did not cause anything to change. So I presume this will be fixed in the next release. Thanks for your time. Ciao, Brian [1] http://cygwin.com/faq-nochunks.html#faq.setup.snapshots -- 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