X-Spam-Check-By:	sourceware.org
Date:	Mon, 16 Apr 2007 13:20:14 +0200
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: tcsh-6.15.00-1 can't find cat, cut, sed
Message-ID:	<20070416112014.GB5799@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<20070413232335 DOT GA27411 AT nuthaus DOT mib DOT org> <20070416103426 DOT GA5799 AT calimero DOT vinschen DOT de> <019401c78015$ce444e40$2e08a8c0 AT CAM DOT ARTIMI DOT COM>
Mime-Version:	1.0
In-Reply-To:	<019401c78015$ce444e40$2e08a8c0@CAM.ARTIMI.COM>
User-Agent:	Mutt/1.4.2.2i
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
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

On Apr 16 11:55, Dave Korn wrote:
> On 16 April 2007 11:34, Corinna Vinschen wrote:
> 
> > On Apr 13 16:23, Keith Thompson wrote:
> >> I just upgraded to tcsh 6.15.00-1.  When I start a login shell,
> >> I get the following error messages:
> >> 
> >> cat: Command not found.
> >> cut: Command not found.
> >> cat: Command not found.
> >> cut: Command not found.
> >> sed: Command not found.
> >> [...]
> 
> > Hang on, I'm wondering how this is supposed to be a bug.  When you start
> > a local Cygwin shell, the cygwin.bat script sets $PATH for you, so that
> > it contains /bin.  [...]
> 
>   Besides, if you startup tcsh on a linux box with an empty $PATH, you'll get
> the exact same problems, so Cygwin is DTRT-ing here!  Here's an example:
> [...]

Oh, hmm, I just found that /cygwin.bat does *not* set $PATH.  And I was
so sure it does... at least mine does when starting tcsh.   And as the
login shell in an ssh session it gets a valid $PATH anyway.

Otherwise $path is (correctly) set in /etc/csh.login, but which is
sourced *after* sourcing /etc/csh.cshrc.  This is rather unfortunate.
I'm wondering if I should just compile tcsh with the LOGINFIRST flag
set, which turns around the order in which cshrc and login files are
sourced...


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
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 -