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: Mon, 22 Oct 2001 12:47:07 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: more info on execvp problem
Message-ID: <20011022124707.A8721@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <3BD3EA44 DOT FF96A58A AT syntrex DOT com> <20011022112817 DOT C7609 AT redhat DOT com> <3BD43CF4 DOT 2611ABC3 AT syntrex DOT com> <3BD43DE9 DOT 9060205 AT ece DOT gatech DOT edu> <3BD43F41 DOT 6FCAFB94 AT syntrex DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3BD43F41.6FCAFB94@syntrex.com>
User-Agent: Mutt/1.3.21i

On Mon, Oct 22, 2001 at 05:46:09PM +0200, Pavel Tsekov wrote:
>Charles Wilson wrote:
>> 
>> Pavel Tsekov wrote:
>> 
>> > I was sure there will be a response like this - in short since as we
>> > both
>> > agree is posix internally (if noone messed with it) - you get this as
>> > result
>> > of getenv("PATH"):
>> >
>> > c:/jdk1.3.1/bin:/usr/local/bin:...:c:/usr/local/emacs/bin
>> 
>> Listen carefully: as Chris has already pointed out, that is NOT a posix
>> path.  THIS is a posix path:
>> 
>> /cygdrive/c/jdk1.3.1/bin:/usr/local/bin:...:/cygdrive/c/usr/local/emacs/bin
>
>Now as I see a hostility in you statement I would suggest you to fire 
>you debbuger and try the little test found in my first e-mail:
>
>I try to explain that the first "c" is not drive C:
>
>Consider the following DOS style PATH:
>C;C:;C:\WINNT\System32 for exmaple
>this is  
>
>1. C directory C in current directory
>2. C: for drive C: root folder
>
>now put this path in PATH launch the debugger and see what is 
>the output of getenv 

The light dawned.  I finally understand.  Sorry for being so dense.

newlib's execvp had some very obsolete cygwin considerations.  It shouldn't
be trying to accomodate a Windows path.  I have no idea when that was ever
a good idea but it is definitely not a good idea now.

I've just nuked all of the strange path handling code from execvp and allowed
it to do the right thing.

Actually, hmm.  I think I'll move all of the execvp handling into cygwin where
it belongs.

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/