X-Recipient: archive-cygwin AT delorie DOT com
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
MIME-Version: 1.0
In-Reply-To: <010201cd4f24$d2eeba50$78cc2ef0$@motionview3d.com>
References: <CAOytrNAmA+Y6DrcG5T-NdVrEGLTZRWhbOEVjMh4=-_Y8xiUNjg AT mail DOT gmail DOT com>	<010201cd4f24$d2eeba50$78cc2ef0$@motionview3d.com>
Date: Fri, 22 Jun 2012 12:11:26 -0700
Message-ID: <CAOytrNDKpnZUHgMAkKxnfEy=1p-OL97AMAXe03GknMtJnTkX=g@mail.gmail.com>
Subject: Re: stdout not visible on some programs after upgrading from to 1.7.11-1 to 1.7.15-1
From: Brian Cavagnolo <bcavagnolo AT berkeley DOT edu>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=ISO-8859-1
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id q5MJBrp0025960

On Wed, Jun 20, 2012 at 1:39 PM, James Johnston <JamesJ AT motionview3d DOT com> wrote:
>> -----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
>
> <snip>
>
> 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).

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=pipe_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