Subject: Re: Re: bash running configure gives: '4546276: No such fil
From: [email-masked] ("Mauro Condarelli")

24 Oct 1996 14:22:42 -0700
Sender: [email-masked]
Approved: [email-masked]
Distribution: cygnus
Message-ID: <[email-masked]>
Comments: Authenticated sender is <[email-masked]>
Original-To: [email-masked]
X-mailer: Pegasus Mail for Windows (v2.42a)
Original-Sender: [email-masked]

> Problem: bash does not find executables in the current directory
You mean that U*ix does not automatically add the current directory 
to PATH?

That should be *well* known to all bash users :) :)

To a newbie it should suffice (and IMHO is clearer) to say that "." 
must be *explicitly* added to PATH (and exported).
> 
> Solution: define a HOME variable and have it available to bash when it
> starts (try 
>         bash$ printenv | grep HOME
and "echo $HOME" ????

> to test). Then create a .bashrc with notepad (CR/LF or not doesn't matter)
> and put it
> in the directory pointed by HOME with the following lines (at least):
> 
> PATH=/bin:/usr/bin:/usr/H-i386-cygwin32/bin:/usr/H-i386-cygwin32/lib/gcc-lib
> /://F/WINNT35/system32://F/WINNT35://C/DOS://C/UTILITY:.
> export PATH
*very* installation dependent and doing *much* more than stated 
intentions; try:
export PATH=.:$PATH
to have a DOS-compatible behaviuour, or:
export PATH=$PATH:.
to have an *almost* UNIX-approved behaviour (having . in PATH is 
regarded as an "unsafe" practice).

Regards
Mauro
-
For help on using this list, send a message to
"[email-masked]" with one line of text: "help".