DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:subject:to:references:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=c+nKpsbCg8YDQR+H
	pPbK+vy4Pu7YqRkYsga0rCwlkMeNymN/CF/TTY/4VhqvceMS+KtGrlrXDMbLIm0D
	46mAJcQL3hijy1UIhXtP5XUWY9ta2/qa7BWYM5Ilcm3VUsgunuTkI+5Xtc0XO3fU
	Fn8Sbe9t0P2EAH8UtpBs6EDtKVg=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
From: Franz Fehringer <fehrin2 AT googlemail DOT com>
Subject: Re: antrun versus wsl versus cygwin
To: cygwin AT cygwin DOT com
References: <q4bfgv$2i9q$1 AT blaine DOT gmane DOT org> <01f0b400-b44b-85a7-14bc-6ca4189481c6 AT towo DOT net>
Openpgp: preference=signencrypt
Message-ID: <7adb0a4e-2cf5-0ad8-d479-4fdd509cebf3@gmail.com>
Date: Sun, 17 Feb 2019 14:39:33 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:60.0) Gecko/20100101 Thunderbird/60.5.0
MIME-Version: 1.0
In-Reply-To: <01f0b400-b44b-85a7-14bc-6ca4189481c6@towo.net>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit

Am 17.02.2019 um 13:53 schrieb Thomas Wolff:
> Am 17.02.2019 um 12:11 schrieb Franz Fehringer:
>> Hi all (half off topic),
>>
>> I have installed (on a Windows 10 1809 system) both Cygwin and WSL (only
>> the Windows component, no real Linux distribution yet).
>> This scenario gives me a strange problem with antrun: With <exec
>> executable="bash"> i always get the WSL bash instead of the Cygwin one,
>> although Cygwin is first in PATH (both Cygwin PATH and Windows PATH),
>> even so if C:/Windows/System32 (location of WSL bash) is not in the
>> (Cygwin) PATH at all.
>> I made some tries with extra parameters like seachpath to no avail.
>> It (naturally) works if i give the full absolute path to the Cyhwin
>> bash, but this is awkward.
>> Any hints about reason and solution?
> No, just about some diagnostics (maybe your application does not see the
> extended PATH?): on a Windows cmd line, say `where bash` to see if it's
> really available...
> 

I am not sure if i understand this correctly, but

Windows cmd:

C:\Users\feh01589>where bash
C:\Tools\Cygwin\bin\bash.exe
C:\Windows\System32\bash.exe

C:\Users\feh01589>`where bash`
'`where' is not recognized as an internal or external command,
operable program or batch file

Cygwin bash:

FEH01589 AT MU-N-566 ~
$ where bash
C:\Tools\Cygwin\bin\bash.exe
C:\Windows\System32\bash.exe

FEH01589 AT MU-N-566 ~
$ `where bash`
-bash: C:\Tools\Cygwin\bin\bash.exe: Kommando nicht gefunden.

where is only available as a Windows executable (not a Cygwin one).


--
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