Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sources.redhat.com
Message-ID: <3A0FC9B7.254F45CC@redhat.com>
Date: Mon, 13 Nov 2000 12:00:07 +0100
From: Corinna Vinschen <vinschen@redhat.com>
Reply-To: cygwin <cygwin@sources.redhat.com>
MIME-Version: 1.0
To: cygwin <cygwin@sources.redhat.com>
Subject: Re: TCSH 6.08.00 *.exe problem
References: <047f01c04d5b$a6edf830$365aa8c0@ise.ch>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Anatol Studler wrote:
> 
> Corinna
> 
> I'm using the TCSH 6.08.00 in my cygwin environment, and I have following
> problem with it, which works with BASH:
> 
> ----------------------------
> [CYGSERV] ~ > tcsh
> [CYGSERV] ~ > CL.EXE
> CL.EXE: Command not found.
> [CYGSERV] ~ > bash
> bash-2.04$ CL.EXE
> Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 12.00.8804 for 80x86
> Copyright (C) Microsoft Corp 1984-1998. All rights reserved.
> 
> usage: cl [ option... ] filename... [ /link linkoption... ]
> bash-2.04$
> ----------------------------

I didn't look into the sources of tcsh for months. I simply tried it
and you're right. However, typing `cl' works. The reason is that
if running under Cygwin the shell creates it's hash table so that
executables which end in .exe or .com are shortend by that extension
and executables ending in .EXE or .COM are shortened _and_ changed
into lower case before being inserted into the hash table. The source
code is in sh.exec.c, line 748ff. Feel free to change it to your
needs.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                        mailto:cygwin@sources.redhat.com
Red Hat, Inc.
mailto:vinschen@redhat.com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com