Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <001201c31d95$fafad120$78d96f83@pomello> From: "Max Bowsher" To: Cc: References: <16071 DOT 62978 DOT 20742 DOT 367143 AT gargle DOT gargle DOT HOWL><001c01c31d8a$3dbe4d40$78d96f83 AT pomello> <16072 DOT 5319 DOT 377807 DOT 761155 AT gargle DOT gargle DOT HOWL> Subject: Re: Using Cygwin on NT 4.0 and Win2000; a user experience Date: Mon, 19 May 2003 00:34:08 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Martin Buchholz wrote: >>> - The "grep" package comes with a grep.exe (and no file "grep"), but >>> no egrep.exe (instead it has a "egrep"). Of course this is easy for >>> the user to fix, but the package should be fixed as well. > > Max> There is nothing wrong here - it doesn't need to be fixed. > > There is non-zero support in Sun's Java SDK to allow building using > Cygwin tools (although MKS is the "official" supported platform). > In one of the Makefiles is this line: > > EGREP = $(UNIXCOMMAND_PATH)egrep.exe > > Arguably, this is bad code. You should run a command via its name, > sans any .EXE extension. But Cygwin should be consistent; either all > executables are named FOO, or they're named FOO.EXE. Make up your mind. Except that we are consistent. *Real* executables have an .exe suffix. Symlinks don't. Max. -- 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/