Mail Archives: cygwin/2001/05/27/23:06:07
Once you find where cygcheck actually is using Windows Explorer's find file
facility, you can execute it by giving the exact directory location. For
example if it is in c:\some_other_dir\, you should be able to run it in the
MSDOS shell by typing:
c:\some_other_dir\cygcheck -s -r
You should also be able to execute it from bash as:
c:/some_other_dir/cygcheck -s -r
/bin and /usr/bin should be the same directory (normally c:\cygwin\bin) if
your mounts are correct; the same applies to /lib and /usr/lib. I recommend
deleting your entire installation and using setup.exe to "Install from
Internet" into the default location (c:\cygwin\). You probably should
remove all the registry entries under "HKEY_CURRENT_USER\Software\Cygnus
Solutions" and "HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions" first.
--
Mac :})
Give a hobbit a fish and he'll eat fish for a day.
Give a hobbit a ring and he'll eat fish for an age.
----- Original Message -----
From: "Ron Elliott" <celliott AT ns DOT sympatico DOT ca>
To: <cygwin AT cygwin DOT com>
Sent: Sunday, May 27, 2001 18:40
Subject: Re: Bash wont recognize any commands
> Well, see. Nothing works. I cant even use cygcheck.. Heheh. Um, I can
however,
> use any of the commands that are default in the cygwin/bin directory (eg.
find,
> byacc, locate, time. And obviously exit and logout). Even if I move
something
> into that directory it wont recognize it. Thats what I found strange. I
cant run
> anything besides those few commands that the executable resides in the
/bin
> directory by default. Everything else is in /usr/bin. Im using the latest
> version of everything. Downloaded I have ash, cygwin, gcc, make,
fileutils,
> binutils, and a few others. I downloaded just what I needed for
compilation of
> C/C++ source code since Im on a modem :)
>
> For example, when I start up bash, it says:
> BASH: id: command not found.
> BASH: mkdir: command not found.
>
> And those commands are in usr/bin as they should be. Ive tried changing my
> DOS/Windows (whatever you want to call it) PATH in many different
combinations
> and nothing works correctly. I can get the commands to work under a DOS
prompt,
> but they dont work correctly (for some reason they cant call each other
> recursively, nor does it look in the right place for the commands).
However
> changing this path seemed to have no effect on Bash, so I assume it is
> non-relevant. Everything is default as it is when installed.
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
- Raw text -