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:to:subject:date:message-id:references
	:in-reply-to:content-type:mime-version
	:content-transfer-encoding; q=dns; s=default; b=McQJ2yMV5OWdj5FY
	JP8GpRomZ5Dn70QLrBfa90fIqhXQd5OpbGPsMkY53PaNjGv5zCZT5pQBR/e2M524
	nVsfEr+0TkP5OretSv27R0t3qDWucsqUN6pMte7qWmlWiC9VJGM7ZPI2UphGzRLk
	NjfZUGoE8IseSiM7tv4UtcTV5/0=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
From: "Soegtrop, Michael" <michael.soegtrop@intel.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: Unexpected behavior of ~ when calling bash from a different cygwin installation
Date: Fri, 15 Jun 2018 13:32:08 +0000
Message-ID: <0F7D3B1B3C4B894D824F5B822E3E5A177880079D@IRSMSX102.ger.corp.intel.com>
References: <0F7D3B1B3C4B894D824F5B822E3E5A1778800706@IRSMSX102.ger.corp.intel.com>
In-Reply-To: <0F7D3B1B3C4B894D824F5B822E3E5A1778800706@IRSMSX102.ger.corp.intel.com>
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit

Dear Cygwin Users,

I got it, I just have to clear the HOME variable before.

But I have a few more observations on this:

the FAQ (section 4.20) state that the root path for the mount table depends on the path of the cygwin1.dll, to which an executable is linked. This doesn't seem to be the case. E.g. when I do

* start a bash via C:\bin\cygwinA\cygwin.bat 
* cd to /cygdrive/c/bin/cygwinB/bin
* ./bash

The first and the second bash have both /=C:\bin\cygwinA although SysInternals ProcExplorer clearly shows that the second bash loads the cygwin1.dll from C:\bin\cygwinB and not from C:\bin\cygwinA. Is there some description on how the path mapping really works?

If I do:

* start a bash via C:\bin\cygwinA\cygwin.bat 
* cd to /cygdrive/c/bin/cygwinB/bin
* /cygdrive/c/Windows/System32/cmd
* bash

The dlls to which the second bash links are the same in both cases, but in the second case /= C:\bin\cygwinB in the second shell.

And yes, I also read in section 4.20 of the FAQ that one shouldn't call one Cygwin from another. But I think a clear handover from one bash to another should work in a documented way.

Best regards,

Michael

Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Christian Lamprechter
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928


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