delorie.com/archives/browse.cgi | search |
Mailing-List: | contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm |
Sender: | cygwin-owner AT sourceware DOT cygnus DOT com |
Delivered-To: | mailing list cygwin AT sourceware DOT cygnus DOT com |
Message-ID: | <3709FD2D.809AF17@mcd.alcatel.be> |
Date: | Tue, 06 Apr 1999 14:25:17 +0200 |
From: | "R. Hickling" <hicklinr AT mcd DOT alcatel DOT be> |
X-Mailer: | Mozilla 4.5 [en] (WinNT; I) |
X-Accept-Language: | en |
MIME-Version: | 1.0 |
To: | "cygwin AT sourceware DOT cygnus DOT com" <cygwin AT sourceware DOT cygnus DOT com> |
Subject: | Shell scripts under Cygwin32 |
I'm attempting to compile some 'GNU type' applications under cygwin32 (or, more specifically: CYGWIN_NT-4.0 20.1 (0.3/1/1) 1998-12-3 20:39:18 i686 unknown which is the output of uname -a minus local stuff). I find that when I go ./configure at the command line I get bash: ./configure: No such file or directory So I have to go sh configure This is only mildly irritating, but of course scripts like 'configure' contain many calls to other scripts - and these require 'sh' to be prefixed to them too - since first lines of !# /cygwin/bin/sh (for example) don't seem to work either. I would be surprised if it's really necessary for me to go and modify the whole script ... Anyone know what's wrong here? -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |