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: Tue, 26 Jun 2001 16:13:58 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Patch: Bug: Shell fork/exec avoidance in make-3.79.1-3
Message-ID: <20010626161358.A15953@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <17B78BDF120BD411B70100500422FC6309E2CE AT IIS000>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.11i
In-Reply-To: <17B78BDF120BD411B70100500422FC6309E2CE@IIS000>; from Dautrevaux@microprocess.com on Tue, Jun 26, 2001 at 08:56:50PM +0200

On Tue, Jun 26, 2001 at 08:56:50PM +0200, Bernard Dautrevaux wrote:
>> I've included a patch below that changes all the char[] definitions
>> in job.c to char*.
>
>I don't think that is the problem; if I look at your patch below, the char[]
>definitions you change in char* are only used on AMIGA or VMS, but *NOT* on
>CYGWIN... ;-(

Sorry, no.  The original poster obviously did some research here.  There
is a definite problem between 'char *' and 'char []' in the
default_shell definition.

>If you look at my previous message (posted about in paralell with your),
>you'll see that just recompiling the code without any change allow me to get
>a working make. I suspect your change (that does nothing on CYGWIN) is just
>exercising the same behaviour. IMHO it's just the cygwin package that was
>compiled in a buggy environment. 

I build make on linux, like all of my packages.  To the best of my knowledge,
I have never had a corrupted environment.  I build everything in a standard
way using standard scripts.  If I detect an error, I correct the script.

>IIRC it happens some time ago to Corinna to have a screwed-up environment
>that generated a working bash that shows a bug that disapear after she
>updates its environment. I suspect the make maintainer have (or had) the
>same problem...

I suspect that your suspicion is wrong.

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/