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: Sat, 16 Jun 2018 11:13:00 -0000 [thread overview]
Message-ID: <0F7D3B1B3C4B894D824F5B822E3E5A17788010BF@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <1307619899.20180616023803@yandex.ru>
Dear Andrey,
> The mapping is consistent throughout the execution tree.
I would like to understand the underlying mechanism. The documentation (FAQ section 4.20) states (as far as I understand) that the Windows path of the Cygwin system root an executable sees is the parent directory of the folder in which the cygwin1.dll resides which is loaded by an executable. As I showed, this doesn't seem to be the case. How does it work then? How is the system root folder passed from parent to child?
> At best, nothing will work
Actually if I put cmd in between and clear a few environment variables it works very well in fairly complicated scenarios. Still I would like to understand how the underlying mechanisms work (preferably without reverse engineering).
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
next prev parent reply other threads:[~2018-06-16 8:14 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 [this message]
2018-06-16 13:06 ` Marco Atzeri
2018-06-16 18:27 ` Soegtrop, Michael
2018-06-17 2:14 ` cyg Simple
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=0F7D3B1B3C4B894D824F5B822E3E5A17788010BF@IRSMSX102.ger.corp.intel.com \
--to=michael.soegtrop@intel.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).