I guess I found the answer to my own question. Since some other people
have had this same problem, here is the solution.
There is a problem with the PATH environment under Win 2000. To
identify the problem I typed the following in DOS:
bash -c "which sort"
I got a response of "/cygdrive
On Tue, 29 Jul 2003, Lisbeth Kellogg wrote:
> I guess I found the answer to my own question. Since some other people
> have had this same problem, here is the solution.
>
> There is a problem with the PATH environment under Win 2000. To
> identify the problem I typed the following in DOS:
>
age-
From: Elfyn McBratney [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 29, 2003 4:33 PM
To: Lisbeth Kellogg
Cc: [EMAIL PROTECTED]
Subject: RE: Problem call a cygwin command from a dos batch file
On Tue, 29 Jul 2003, Lisbeth Kellogg wrote:
> I guess I found the answer to my own question.
/g/
C:\cygwin\bin>
-Original Message-
From: Lisbeth Kellogg [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 29, 2003 4:40 PM
To: [EMAIL PROTECTED]
Subject: RE: Problem call a cygwin command from a dos batch file
Yes, that would fix it. But I think we have a bug here. In cygwin I
get:
ECTED]
Subject: RE: Problem call a cygwin command from a dos batch file
My /etc/profile (the default one with cygwin) contains this: export
PATH="/usr/local/bin:/usr/bin:/bin:$PATH"
which implies that the behavior you are seeing is to be expected (if you
have the same /etc/profile).
See what
gg
>
> -Original Message-
> From: Elfyn McBratney [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, July 29, 2003 4:33 PM
> To: Lisbeth Kellogg
> Cc: [EMAIL PROTECTED]
> Subject: RE: Problem call a cygwin command from a dos batch file
>
>
> On Tue, 29 Jul 2003, Lisbe
Lisbeth Kellogg wrote:
> Yes. Now I get the same thing. But why don't I have to do it that way
> in XP?
It's nothing to do with the OS or Bill Gates' conspiracies.
Consider the two *machines* as distinct entities, and examine their
configurations (all environment variables, all .rc scripts) to
7 matches
Mail list logo