Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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
Message-ID: <42BFF606.5000706@byu.net>
Date: Mon, 27 Jun 2005 06:50:14 -0600
From: Eric Blake <ebb9 AT byu DOT net>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
MIME-Version: 1.0
To: Christian Matuszewski <C DOT Matuszewski AT gmx DOT de>
CC: cygwin AT cygwin DOT com
Subject: Re: bash and make are trapped in an endless loop
References: <25607 DOT 1119872520 AT www48 DOT gmx DOT net>
In-Reply-To: <25607.1119872520@www48.gmx.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Christian Matuszewski on 6/27/2005 5:42 AM:
> Hi,
> 
> if i start a fresh cygwin shell and I enter an asterisk at the prompt:
> $ *
> then nothing happens. That's OK, although one could expect a message like:
> "bash: *: command not found".

Typing * as your command normally expands into a list of all the files in
that directory, then tries to execute the first file in that list (try
"echo *" to see what would happen).  Your desired error message will only
occur if filename expansion is disabled, such as by using "set -f".

Beyond that, the behavior that you get from typing * (or letting make type
it), depends on your current directory.  Based on your report, I'm
guessing that your first directory was empty, or started with a file that
was executable and did nothing; but when you switched to the directory
where your Makefile was, you happened to get a first filename listed that
was treated as a program and which entered into an infinite loop (the
infinite string of y's tends to imply that somewhere you invoked
/bin/yes).  But this behavior is not unique to cygwin.

- --
Life is short - so eat dessert first!

Eric Blake             ebb9 AT byu DOT net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCv/YG84KuGfSFAYARArPzAJ4l6wnWniptdsueqwN/wgRfzB8pxACdEbFG
CxStu2UEiJGCkhM04NKxKZE=
=oLZK
-----END PGP SIGNATURE-----

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