Mail Archives: cygwin/2005/09/21/10:57:39
Thank you very much all for your replies. I think I should clarify
somthing first. Windows has two places to set path parameters "Local
Machine" and "User environment", what I changed is "local machine" one
which means it affects anyone use this pc.
1. I do have /cygwin/bin in my "User environment" Path, and I can see
cygwin find and use them all by type "env" in cygwin.
2. I didn't install make (gnu one) yet. I just want to delete borland
path first, because by accidently I typed make, it called borland
"make".
3. So, I can type "bash" in any directory in CMD prompt. It is like
the followings:
####################################################
H:\>bash
bash: .bash_profile: No such file or directory
bash-3.00$ //enter bash environment without problem
bash-3.00$ exit
exit
H:\>bash --login
H:\> //It is back to CMD prompt !!
###################################################
I fixed this now, because I stupidly put line ". .bash_profile" in
".bashrc" file to ensure my .bash_profile can be called every time
when I start cygwin. and .bash_profile calls .bashrc again. I think it
loops.
Many thanks for all of your advices.
Leo
> ----Original Message----
> >From: faif cn
> >Sent: 21 September 2005 10:04
>
> > Thank you Dave
> >
> > On 9/20/05, Dave Korn wrote:
> >>>
> >>> I deleted some values in Windows Local Environment variable "PATH".
> >>> My original "HOME" is c:/home/myname/. And then:
> >>
> >> .... it broke. So put them back!
> >
> > 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
> >
> >
> "%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\"
>
> Get rid of that double-semicolon between %HTC_PIC%\BIN and the GTK path.
>
> > 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.
>
> Meaning this behaviour ?
>
> >> If I type "bash" in any other directories, the bash promote can be
> >> shown successfully and I can use bash environment.
> >>
> >> If I type "bash" in my home directory, it just hangs for seconds and
> >> back to dos promote and nothing happened. Alternatively "bash --login"
> >> has same behavior.
>
> You must have a file called bash in your home directory, and that empty
> component between the two double-semicolons counts as adding '.' to your
> $PATH in POSIX.
>
> cheers,
> DaveK
> --
> Can't think of a witty .sigline today....
>
>
> --
> 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/
>
>
--
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/
- Raw text -