Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
Date:	Wed, 30 Mar 2005 11:01:10 -0500
From:	Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: cygexec mounted binaries don't inherit PATH during dynamic loading
Message-ID:	<20050330160110.GA4621@trixie.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
References:	<424A3A3D DOT A4484691 AT dessent DOT net>
Mime-Version:	1.0
In-Reply-To:	<424A3A3D.A4484691@dessent.net>
User-Agent:	Mutt/1.5.8i

On Tue, Mar 29, 2005 at 09:33:49PM -0800, Brian Dessent wrote:
>So my question is simply this: in the case of spawning a cygexec-mounted
>binary, shouldn't build_env at least fill in PATH from the calling
>process' value, so that Windows can do its runtime DLL loading?

Yes, it should.  I've been closing my eyes to this problem for a while but
this is the second time it's been reported in the span of a week (the other
time was over in the crossgcc mailing list).

There were several problems with the handling of PATH and other special
environment variables.  I hope I have fixed all of them in CVS.  A new
snapshot is being generated now.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -