This is the mail archive of the
mailing list for the Cygwin project.
Re: path dependent on drive in cygwin
- From: "Larry Hall (Cygwin)" <reply-to-list-only-lh at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Tue, 30 Jun 2015 22:00:42 -0400
- Subject: Re: path dependent on drive in cygwin
- Authentication-results: sourceware.org; auth=none
- References: <d27ec3eeb72a8a214154779bba6f2c38 at imap dot force9 dot net>
- Reply-to: cygwin at cygwin dot com
On 06/30/2015 02:27 PM, John Norris wrote:
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
I think we need to see your path in Windows and your cygcheck output.
Start cmd.exe and send the results of "PATH".
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple