X-Spam-Check-By: sourceware.org Date: Tue, 7 Feb 2006 13:02:38 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: strange cygstart bug with current Cygwin versions Message-ID: <20060207180238.GA18679@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: <2fc802c00602031305p7574f255g5e67e44cd8b754e AT mail DOT gmail DOT com> <2fc802c00602061329x56784831mb5ab16a12191b2e AT mail DOT gmail DOT com> <43E7D056 DOT 10505 AT mscha DOT org> <20060207023104 DOT GA2484 AT efn DOT org> <43E8E00F DOT 2060903 AT mscha DOT org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43E8E00F.2060903@mscha.org> User-Agent: Mutt/1.5.11 Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Tue, Feb 07, 2006 at 06:59:43PM +0100, Michael Schaap wrote: >On 7-Feb-2006 3:31, Yitzchak Scott-Thoennes wrote: >> On Mon, Feb 06, 2006 at 11:40:22PM +0100, Michael Schaap wrote: >> >>> What we basically need to do, is copy the Cygwin environment to the >>> Windows environment, taking care of path conversion for all the >>> appropriate variables. >>> >> >> Maybe start with: >> >> http://www.cygwin.com/ml/cygwin-patches/2005-q4/msg00009.html >> > >Not really, I think, especially since that code didn't make it into >Cygwin. ;-) >(Also, Corinna suggested in that thread that an application should >simply convert the necessary variables itself.) > >I did notice, though, that a new version, setup_winenv(), externally >callable as cygwin_internal(CW_SETUP_WINENV), was made available ... >last Thursday. (Looks like the code was adapted from the cygstart code, >actually. :-) ) >So, ideally, that function would be fixed to do POSIX to Windows >conversion on the necessary variables, and cygstart can then be changed >to call it, instead of its own setup_win_environ() function. > >That would mean that the bug won't be fixed until 1.5.20 is released, >though ... >So, I guess I'll just add some path conversion handling to the cygstart >code itself, for now. Then if at some point the Cygwin setup_winenv() >function is fixed in a similar way, and released, I might take it out >and call cygwin_internal(CW_SETUP_WINENV) instead. I believe that Brian Ford is looking into modifying the new CW_SETUP_WINENV code to perform the proper conversion of POSIX style to Windows style. 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/