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=huIcAjcHtLe5hdiw
	HMkIaI5KQAfe4bont02TYVqX4myc8QwBQTny4BF7UpXHCYYPv5+2BsmqKP2HfhpJ
	h/ElbcqnnEKw3MynJk0dqvi+BWQdxCqu3J9VV6zaN17dLsUTXBjIdK0t28ApZ0IB
	BeqDqQzpdJQExOxUjKXIRpTZ5zY=
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=1LZppWGxBK7oy/ywSr96by
	G70sI=; b=lTcntSQ4xeC7yUwz1DAQD1tJW2W8Ic/TpwqhByYS2DBszn4+BkY2Rf
	QtUyha7kTXaXwzOjG4YKOhczRPLJBa9dANszacBZFeanQ7MDZxXACbaFlx6qSK9E
	jnQBVHyIhmsc+fJrMpi9shCE5qMEt97rQtSCTIh/ubdzLYKxnOhms=
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=BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=resident, HX-Received:c687, dear, Dear
X-HELO: mail-wm0-f52.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:message-id:date         :user-agent:mime-version:in-reply-to:content-language         :content-transfer-encoding;        bh=Y3vH1UgXEx3JHJjgAZfn/RN+6pylXISlLVTsz5qfRKA=;        b=hsYrPMAt6Ak91LcdIhd9ogQ8Hj4lqG1yfihLAI52aSO9uJ12Z1f8ECj/iRA9jh5Enl         P/GqaSbSJS3VmpBAq9BJSnM3AbY7OHs2XXND1oFrn41lbdgnOnGyeGPVw1QE4Jgy9N90         roRAySpJoKURGOhjlzXxF0SQ7Y0AofUmXUnPxKM08acZDaxtB3tkH/1SPVlpSfT+1oqg         BvDZf2HujvYPNYmyGgOfRhc4aZEpb4VHBkAGgD/wuNHIJAOsXh0F9NGAXWBKrgFjtdkn         8EsR+OT2h9hUz8lOWM2FwQJKqPbvnM5oFi6Llr25k6/qT1ODOVIUNYwqZFI4bXTdFSfg         DQbQ==
X-Gm-Message-State: APt69E0eYrMjcL3ejyNIykXQS7i9cTTeZ+6JuKuGSuf5YOZ52CkayqSU	Kapwcn52ipZwQxlFnVhgbJXzBXBC
X-Google-Smtp-Source: ADUXVKKq0oALL/YeWanvQeUxPFKfv/IvHaTRRxbyIEJ0O3WgMrpP3pmcCislEU3dxvkzS46bhn4NEg==
X-Received: by 2002:a1c:c687:: with SMTP id w129-v6mr3629658wmf.66.1529142403417;        Sat, 16 Jun 2018 02:46:43 -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>
From: Marco Atzeri <marco DOT atzeri AT gmail DOT com>
Message-ID: <3a183948-c9f5-bf7a-355e-9d194c5a5974@gmail.com>
Date: Sat, 16 Jun 2018 11:46:41 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <0F7D3B1B3C4B894D824F5B822E3E5A177880079D@IRSMSX102.ger.corp.intel.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

On 6/15/2018 3:32 PM, Soegtrop, Michael wrote:
> 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?
> 

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

I have the same issue when testing a new version of
GraphicsMagick perl interface

The perl program located in /usr/bin will alway use the installed
GM dll's  in the same directory instead of the new one I am trying
to test.



Regards
Marco





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