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
Date:	Thu, 1 Nov 2001 13:08:24 -0500
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: recursive make cause core dump in cygnwin 1.3.3 ?
Message-ID:	<20011101130824.A650@redhat.com>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<01110110032900 DOT 17007 AT etp2 DOT bitmover DOT com>
Mime-Version:	1.0
In-Reply-To:	<01110110032900.17007@etp2.bitmover.com>
User-Agent:	Mutt/1.3.21i

On Thu, Nov 01, 2001 at 09:49:46AM -0800, Andrew Chang wrote:
>I had a problem triggered by recursive make too.  they may be related.
>It turn out the new ash is loosing data when it process "Here document"
>(i.e.  i/o rediection).  I got a empty file.  "Here document" are used
>a lot in configure script.  After two hours, I finaly track it ash.
>After switching back to a older ash release (20010129), it worked fine.
>I did need to re-compile the ash source against the new cygwin dll to
>get it to work however.
>
>Hope this is useful info

So, your theory is that the problem which I reported on September 12 is being
caused by a new version of ash, released on October 18?

Sorry.  I don't think this is helpful.

cgf

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

- Raw text -