Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Message-Id: <200207091443.g69Eh2N01942@etp1.bitmover.com>
Content-Type: text/plain;
  charset="iso-8859-1"
From: Andrew Chang <awc AT bitmover DOT com>
To: "Johan Bezem" <jbezem AT csksoftware DOT com>
Subject: Re: The "make" command and file handle problem
Date: Tue, 9 Jul 2002 07:43:02 -0700
Cc: cygwin AT cygwin DOT com
References: <200207090501 DOT g6951Mo14832 AT etp1 DOT bitmover DOT com> <200207091346 DOT g69Dk1N01866 AT etp1 DOT bitmover DOT com> <3D2AF0AC DOT F0ABEE30 AT csksoftware DOT com>
In-Reply-To: <3D2AF0AC.F0ABEE30@csksoftware.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit

On Tuesday 09 July 2002 07:18 am, Johan Bezem wrote:
> Did you specify a specific SHELL in your makefile? Which version of which
> shell are you using? 
I used ash-20020131-1, 
I also tried bash, it failed differently, but still failed.
> Since CMD.exe cannot handle your "here docment",
> you'll be using another shell, I presume (bash? sh/ash?). I assume that
> you've checked that your "stuff" is actually producing something...
yes, "stuff" are a literal string.
> Any messages on stdout/stderr? 
nope...
> Did it run before, if yes, under which
> configuration?
This has been broken on older cygwin release too..
but differently, on older cygwin release, I have to use
a old version of ash for it to work. If I use the latest ash,
it break my build. (same symptom as reported above)
As of cygwin1.3.12, even my old
ash does not work, so I have to come up with a
new workaround. I did tried to debug the "make" 
source code, but that is getting too messy, so I back off.

>
> Hey, you know what kind of description to give!
> If there's a real problem there, I'd like to know about it (approx. 40
> developers depending on my makefiles...);
> If you didn't solve the right problem, you might want to know about this
> too ;-)
>
> Johan Bezem
>
> Andrew Chang wrote:
> > On Tuesday 09 July 2002 01:23 am, Johan Bezem wrote:
> > > 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.
> > >  make-3.79.1-7
> > > 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?
> >
> > The low level make runs a configure script, which
> > uses a "here document", like so
> >
> > cat >outfile <<EOF
> > stuff
> > stuf
> > EOF
> >
> > The outfile is empty after the above command is done.
> > (note: the low level make is just compiling the standard gnu "patch"
> > source, there is nothing special about this target)
> > Unfortunately I have not come up with a minimin test case yet, sorry.
> > The dos shell workaround do work, however.
> >
> > > 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/

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