X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=h8o1ENuIdDEjcRGA
	Rb6Ne4AbzSi663iN25DKD9stpRdZPaCc5tX9cSV3nlKPBueGek8eDWJy26qLKL9j
	QC7Df1QhNQIEDtJFlufLCulAwO38VjHcSu5RrGm61gQwzrbIQvYxRaiOyJpVo/6+
	XqyudxWNnzEjEZOk15ZQnsd+U0s=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=KmUivIYCnF6AOn5xi0CBcE
	P7nt8=; b=jdez7i8TgGdCwEpBjlPrlyH/PePLa3RJmTt/f3ryoklYrkFeVT/e85
	HC54DMsHrQ6Wih+PoGaqh/GrUZkBaq1LDDFeCXqJx5+wPeHQZOG9RmKXfc7eRftc
	vud5rXfYDiPPXUAFOUWK1nyiMYkGwgtkpug2hcA5MlJWffOiDis3c=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=Having
X-HELO: mail-io0-f179.google.com
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;        d=1e100.net; s=20161025;        h=x-gm-message-state:subject:to:references:from:openpgp:autocrypt         :message-id:date:user-agent:mime-version:in-reply-to         :content-language:content-transfer-encoding;        bh=J+WsgGsE0GAw7uLn0FAkSN7cwcg5nhcb4w+Ds8AM7I8=;        b=M1JIidia3m+ybrFxEvRPq5Ri+gYc4BINqdVRxGuxr9ux1CLBK0zNqC7dsOSDqgoQV/         XkOrDCJBVFr3+3lfh5Nuh46OwJ2ZxBwgZlpxJktrzRaZqrlWu3D/0cddp4weNnvXj9lM         YPAJL5FeqJuAaf/xX+nCp7JSS8qELnTrt9nn5yiml7YKh1hj2+1QDPJQg3InaVBVUlq+         wSNFXB6OxQEkMgraahdpcAvRtXDf+WqOCiojp5Mp5Vvj7NeDDynMh+Ir4QG/5Gy0RA1w         kgn5LwnEnqLrTQE7TB1VmAfrawbY/gU8T4izMvVW0Ra/4+mzWqCoH7U9vyvaQFdnxpa7         g7Bg==
X-Gm-Message-State: APt69E3uTUemgOHbzFaV8hGUEAxDyzZWSUP6sgKjzFsKCrQIt/hwGta6	9uGCXMuHPv+s5BzLW8UDA3LVPg==
X-Google-Smtp-Source: ADUXVKISuh1cRhPtS4/YvSTwWJUV/I+z9oZdySdfa88xMQXQXxVh7caohGzp/LWBpnxqsFaDgY5ovw==
X-Received: by 2002:a5e:d60a:: with SMTP id w10-v6mr5647613iom.54.1529181257415;        Sat, 16 Jun 2018 13:34:17 -0700 (PDT)
Subject: Re: Unexpected behavior of ~ when calling bash from a different cygwin installation
To: cygwin AT cygwin DOT com
References: <0F7D3B1B3C4B894D824F5B822E3E5A1778800706 AT IRSMSX102 DOT ger DOT corp DOT intel DOT com> <0F7D3B1B3C4B894D824F5B822E3E5A177880079D AT IRSMSX102 DOT ger DOT corp DOT intel DOT com> <3a183948-c9f5-bf7a-355e-9d194c5a5974 AT gmail DOT com> <0F7D3B1B3C4B894D824F5B822E3E5A177880141A AT IRSMSX102 DOT ger DOT corp DOT intel DOT com>
From: cyg Simple <cygsimple AT gmail DOT com>
Openpgp: preference=signencrypt
Message-ID: <4f66df8e-e0fa-f7b2-4a3a-87655ebf6aaf@gmail.com>
Date: Sat, 16 Jun 2018 16:34:00 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <0F7D3B1B3C4B894D824F5B822E3E5A177880141A@IRSMSX102.ger.corp.intel.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
X-IsSubscribed: yes

On 6/16/2018 9:33 AM, Soegtrop, Michael wrote:
> Dear Marco,
> 
>> this is due to the preference given by Windows to load dll's from the same
>> directory where the program is resident instead of using the ones in the PATH
> 
> yes, this is expected behavior. What is not expected is that the location of the system root in the Windows file system does not depend on the loaded cygwin1.dll.
> 

Cygwin uses the parent of the path containing the cygwin1.dll as the
root path.  Having multiple Cygwin's on disk isn't an issue.  Starting
another session of a Cygwin using cygwin1.dll on a different path is.
It just doesn't work properly.  Your use of windows cmd to clear the
environment and start another session on a different path works because
the children then don't have a reference to the original parent.

-- 
cyg Simple

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