This is the mail archive of the
mailing list for the Cygwin project.
Re: How does Cygwin determine PWD
- From: Andrey Repin <anrdaemon at yandex dot ru>
- To: Wayne Johnson <wdtj at yahoo dot com>, cygwin at cygwin dot com
- Date: Mon, 30 Sep 2013 22:30:01 +0400
- Subject: Re: How does Cygwin determine PWD
- Authentication-results: sourceware.org; auth=none
- References: <1380557054 dot 49989 dot YahooMailNeo at web121506 dot mail dot ne1 dot yahoo dot com> <1380557664 dot 98433 dot YahooMailNeo at web121505 dot mail dot ne1 dot yahoo dot com>
- Reply-to: Andrey Repin <cygwin at cygwin dot com>
Greetings, Wayne Johnson!
> I am upgrading some of our scripts to use the latest version of Cygwin bash
> et. al. and run into an interesting problem that I'm having trouble
> I have put bash, pwd, etc. into a directory called support_tools, and have a
> batch file that does a cd to the support_tools directory and then runs bash
> in order to capture some information.
> In the old version of bash (3.2.49(22)) when we run bash, pwd returns the
> proper cygwinified path, like C:\Program Files
> Under the new bash (4.1.10(4)), when I do pwd I get /support_tools.
> How does bash (or in this case probably one of the cygwin libraries)
> determine the current directory when you start it up?
cygwin expect base files to be located in ../bin relative to the Cygwin1.dll
location, as far as I know.
I suggest you place Cygwin binaries into /support_tools/bin and supply
/support_tools/etc/fstab with desirable mount options.
Andrey Repin (email@example.com) 30.09.2013, <22:27>
Sorry for my terrible english...