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=Xa44D3ZXKgQYjCJc
	LnVhnunLOK3YcKzX0vCSGIVocNu2qE1ieDEOfCMYQ+6ffWdpS9GO+IR+r36so1yR
	PUgJgDdeM9cNK2EN9howRDvUPhSmqMTCjWzxxCwZnBuANiG9YAe6T3OkWbTagwxB
	X+5S6eiBxmhhds/CPQOV8lCH0so=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Sat, 16 Jun 2018 02:38:03 +0300
From: Andrey Repin <anrdaemon@yandex.ru>
Reply-To: cygwin@cygwin.com
Message-ID: <1307619899.20180616023803@yandex.ru>
To: "Soegtrop, Michael" <michael.soegtrop@intel.com>, cygwin@cygwin.com
Subject: Re: Unexpected behavior of ~ when calling bash from a different cygwin installation
In-Reply-To: <0F7D3B1B3C4B894D824F5B822E3E5A177880079D@IRSMSX102.ger.corp.intel.com>
References: <0F7D3B1B3C4B894D824F5B822E3E5A1778800706@IRSMSX102.ger.corp.intel.com>   <0F7D3B1B3C4B894D824F5B822E3E5A177880079D@IRSMSX102.ger.corp.intel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Greetings, Soegtrop, Michael!

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

"Linked" in this case should be read as "first cygwin1.dll loaded".

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

The mapping is consistent throughout the execution tree.

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

Indeed, since you cleanly broke out of cygwin execution tree.

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

It does.
Do not mix Cygwin installations. At best, nothing will work, at worst, you'll
get unpredictable behavior that is hard to track down.
Each Cygwin installation have its own rebase map.


-- 
With best regards,
Andrey Repin
Saturday, June 16, 2018 2:34:34

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