Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Message-ID: <3D2A9D71.E2318ECE@csksoftware.com>
Date: Tue, 09 Jul 2002 10:23:13 +0200
From: "Johan Bezem" <jbezem@csksoftware.com>
Reply-To: CygWin Mailing List <cygwin@cygwin.com>
Organization: CSK Software AG
X-Accept-Language: en,de,nl,el,fr,af,es,it
MIME-Version: 1.0
To: Andrew Chang <awc@bitmover.com>
Cc: cygwin@cygwin.com
Subject: Re: The "make" command and file handle problem
References: <200207090501.g6951Mo14832@etp1.bitmover.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by AMaViS snapshot-20010407

Hi,

Andrew Chang wrote:
> 
> On cygwin1.3.12-1, I am running a multi-level makefile.
> For some reason the top level make seems corrupt the file handle
> of the its sub-process. (redirected i/o no longer works in the sub-process).
> Note that my top level makefile is a very complex makefile, it probably
> works fine if you have a simple makefile.
> Fortunately, I stumble across a workaround; It turns out if you spawn
> the lower level make via the DOS shell, the problem goes away.
> 
> e.g.
> 
> low_level_target:
>         cd sub_dir && cmd /c make low_level_stuff;
> 
> Hope this will save someone sometime...

Without further data as to used versions, this will hardly help anyone. I'm
using a "very complex makefile" (whatever that is) on multiple directory
levels under bash, and I have no problems...
How did you deduce that make is corrupting a file handle?

Regards,,

Johan Bezem
CSK Software AG

--
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/

