Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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
Message-ID: <43315778.1080607@byu.net>
Date: Wed, 21 Sep 2005 06:52:08 -0600
From: Eric Blake <ebb9 AT byu DOT net>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
MIME-Version: 1.0
To: faifcn AT gmail DOT com
CC: cygwin AT cygwin DOT com
Subject: Re: strange behavior of bash
References: <459c63b405092009257b3c3980 AT mail DOT gmail DOT com> <SERRANOHxvZ9aZ1i6bd00000128 AT SERRANO DOT CAM DOT ARTIMI DOT COM> <459c63b4050921020472984018 AT mail DOT gmail DOT com>
In-Reply-To: <459c63b4050921020472984018@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to faif cn on 9/21/2005 3:04 AM:
> 
> What I deleted is "borland c" bin directory to avoid cygwin confusing
> two "make" tools. and maybe some other PATH variables which I believe
> set by some outdated software. It left as

Your cygcheck was hard to read, as it was not a plain-text attachment
(hmm, maybe we could update the problem-reporting instructions to tell
people to create cygcheck.txt instead of cygcheck.out, since there are
mailers out there that wrongly assume every file with an unknown extension
should be transferred with a mime type of application/octet-stream).

> 
> "%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;c:\matlab6p5\bin\win32;C:\PROGRA~1\ULTRAE~1;%HTC_PIC%\BIN;;C:\Program
> Files\Common Files\GTK\2.0\bin\"

At any rate, in your cygcheck, you have the environment variable Path, not
PATH (in Windows, envvars are case insensitive, but not in Unix), so that
can cause problems.  Also, you have an unexpanded variable in your path,
%HTC_PIC%.  Furthermore, cygcheck couldn't even find make, with your path
settings, so I don't see how you were complaining about 2 competing
versions of make.  But it very well could be that you did something weird
when trying to cleanup the Borland flavors of unix tools.

> 
> There is nothing special, the same PC with same path variables run
> cygwin no problem. I just get confused why this behavior happens, and
> with invoke --login parameter.

I'm not familiar with DOS promote.  Is it some other vendor's shell?  Does
it provide its own bash in your home directory, which could explain why
you get a different behavior depending on what directory you are in when
you try to run bash?  Your cygcheck shows that you have . on the Windows
path prior to cygwin\bin.

- --
Life is short - so eat dessert first!

Eric Blake             ebb9 AT byu DOT net
volunteer cygwin bash maintainer
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDMVd484KuGfSFAYARAt9uAKDAhQp+/zw7mKHIn5O4y329bW1NxgCghFFV
DpH4fJzmvi8CCYV1olzct0I=
=2Z0p
-----END PGP SIGNATURE-----

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/