X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:reply-to:message-id:to:subject :in-reply-to:references:mime-version:content-type :content-transfer-encoding; q=dns; s=default; b=CZBHtlNtpcg3heH+ d85Z4sRh8SzZNPMRahm0Cd2MACt5ZOudHe8dLLpDxpDvOQXYq/7POoKPpda7oF9T Bj+4mjrxB0KhSGthSS1JGwsliZjmUKglWLH3R/+VNLgAw2RE8VJO/4hlQfdYl+We PoVxJFsKzL4HkegXbvZ6Rt2ckv8= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:reply-to:message-id:to:subject :in-reply-to:references:mime-version:content-type :content-transfer-encoding; s=default; bh=wvzQYClTJT4DMpPIMshugk zRtQc=; b=czrDRNjGilDesrlk+pjpFsqlRa7jXpSvU0pO5FMExi3RIG2oeXfDXe hGJfB5HXaYSK307jCBWeFCuijCoDN2JHHboMjjO7buKUdknWQMcfuvnCSIq8AVjx qEPi5+im44eOvaQlpr7nL7XRwpX3fcyd2DK+Yx8zOG6LrvvS4KYC8= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: Yes, score=5.9 required=5.0 tests=AWL,BAYES_80,FREEMAIL_FROM,KAM_THEBAT,SPF_SOFTFAIL autolearn=no version=3.3.2 X-HELO: smtp.ht-systems.ru Date: Thu, 2 Jul 2015 19:41:46 +0300 From: Andrey Repin Reply-To: cygwin AT cygwin DOT com Message-ID: <1397793597.20150702194146@yandex.ru> To: John Norris , cygwin AT cygwin DOT com Subject: Re: path dependent on drive in cygwin In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Greetings, John Norris! > Hi, > I am running cygwin 1.7.x on Windows 2008. I realise this may be out of > date but this is what we are using. > I have noticed that the path variable for our build user is dependent > on where "cmd /C" is run from. > Please see below - I have cut back the PATH so that it does not > overwhelm. Notice the extra C; before the non cygwin entries. And when > run from e drive, the C; remains but the c: becomes e:. And this is the > problem - the path when run from c is messy but works. The path when run > from e (which is where we do run from) does not work. > Can anyone explain this. I guess one way round this is to explicitly > call the necessary programs without relying on PATH. But interested why > this happens. > Regards, > John > $ /c/windows/system32/cmd > Microsoft Windows [Version 6.1.7600] > Copyright (c) 2009 Microsoft Corporation. All rights reserved. > C:\>path > path > PATH=C:\Cygwin\usr\local\bin;C:\Cygwin\bin;C;C:\Program Files > (x86)\Microsoft Visual Studio 9.0\Common7\IDE;C;C:\Program Files > (x86)\Microsoft Visual Studio 9.0\Common7\Tools;C; How does it help starting CMD from bash? Start it without bash and show the output of PATH command. Or, better, show the output of cat "/proc/registry/HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Control/Session Manager/Environment/PATH" | tr ";" "\n" cat "/proc/registry/HKEY_CURRENT_USER/Environment/PATH" | tr ";" "\n" Or, even better, > Problem reports: http://cygwin.com/problems.html -- With best regards, Andrey Repin Thursday, July 2, 2015 19:35:07 Sorry for my terrible english... -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple