From: cyg Simple <cygsimple@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Unexpected behavior of ~ when calling bash from a different cygwin installation
Date: Sun, 17 Jun 2018 02:14:00 -0000 [thread overview]
Message-ID: <4f66df8e-e0fa-f7b2-4a3a-87655ebf6aaf@gmail.com> (raw)
In-Reply-To: <0F7D3B1B3C4B894D824F5B822E3E5A177880141A@IRSMSX102.ger.corp.intel.com>
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
prev parent reply other threads:[~2018-06-16 20:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-15 13:34 Soegtrop, Michael
2018-06-15 14:49 ` Soegtrop, Michael
2018-06-16 5:56 ` Andrey Repin
2018-06-16 11:13 ` Soegtrop, Michael
2018-06-16 13:06 ` Marco Atzeri
2018-06-16 18:27 ` Soegtrop, Michael
2018-06-17 2:14 ` cyg Simple [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4f66df8e-e0fa-f7b2-4a3a-87655ebf6aaf@gmail.com \
--to=cygsimple@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).