public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
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: Fri, 15 Jun 2018 14:49:00 -0000	[thread overview]
Message-ID: <0F7D3B1B3C4B894D824F5B822E3E5A177880079D@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <0F7D3B1B3C4B894D824F5B822E3E5A1778800706@IRSMSX102.ger.corp.intel.com>

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?

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.

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.

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

  reply	other threads:[~2018-06-15 13:32 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 [this message]
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

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=0F7D3B1B3C4B894D824F5B822E3E5A177880079D@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).