Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Subject: Re: make error: cannot exec gcc (after many compiles) : Win95 : Cygwin of 9/19/2001
To: Charles Hixson <charleshixsn AT earthlink DOT net>
Cc: CygWin <cygwin AT cygwin DOT com>
X-Mailer: Lotus Notes Release 5.0.5  September 22, 2000
Message-ID: <OFF8213184.18B318A5-ON88256ACD.0076218A@rsc.raytheon.com>
From: "Arthur I Schwarz" <Arthur_I_Schwarz AT West DOT Raytheon DOT com>
Date: Thu, 20 Sep 2001 14:33:29 -0700
X-MIMETrack: Serialize by Router on RWSMTA10/SRV/Raytheon/US(Release 5.0.8 |June 18, 2001) at
 09/20/2001 02:33:34 PM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii



Try:
    ./whatever_you_are_doing 2>&1 | tee > file.txt

(In deference to cfg) this is a work-around which seems to be both
undesireable and workable. It might not be right but it's never wrong.

art



Sent by:  cygwin-owner AT sources DOT redhat DOT com


To:   CygWin <cygwin AT cygwin DOT com>
cc:

Subject:  make error: cannot exec gcc (after many compiles) : Win95 :
      Cygwin of 9/19/2001

<snip>
The out.txt file has been edited to include the error message.
It didn't appear in a simply redirected output file.  Strangely
it didn't appear in a redirected stderr file either:
make > out.txt 2>err.txt
err.txt ends up blank, and out.txt doesn't include the error
message, but it appears on the screen if I don't do a redirection.

<snip>






--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/