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 Date: Wed, 1 Oct 2003 12:06:28 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: awk bug in cygwin 1.5.5 under windows xp Message-ID: <20031001100628.GC11435@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <000001c387fd$1266d2b0$30cea783 AT bt09fischerxp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <000001c387fd$1266d2b0$30cea783@bt09fischerxp> User-Agent: Mutt/1.4.1i On Wed, Oct 01, 2003 at 11:19:10AM +0200, Karsten Fischer wrote: > awk fails when called from the cmd or cmdproxy shell. The shell does not > interpret correctly the link to gawk. Apparently this observation was That's a problem of the shell, not of gawk. The installation procedure of gawk on Cygwin is identical to the installation procedure of gawk on Linux. awk is just a symlink to gawk. > reported several times in the internet. > > Changing all "awk" to "gawk" in my scripts works fine, but a more > elegant solution would be desirable. Using ash, bash, ksh, pdksh, tcsh, zsh would actually help. The Cygwin distribution is not designed to run in a native Windows shell in the first place. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- 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/