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
Date: Mon, 27 Jun 2005 15:15:39 +0200 (MEST)
From: "Christian Matuszewski" <C DOT Matuszewski AT gmx DOT de>
To: cygwin AT cygwin DOT com
MIME-Version: 1.0
References: <42BFF606 DOT 5000706 AT byu DOT net>
Subject: Re: bash and make are trapped in an endless loop
X-Authenticated: #14012025
Message-ID: <21629.1119878139@www9.gmx.net>
X-Flags: 0001
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit

> --- Ursprüngliche Nachricht ---
> Von: Eric Blake <ebb9 AT byu DOT net>
> An: Christian Matuszewski <C DOT Matuszewski AT gmx DOT de>
> Kopie: cygwin AT cygwin DOT com
> Betreff: Re: bash and make are trapped in an endless loop
> Datum: Mon, 27 Jun 2005 06:50:14 -0600
> 
> -----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.
> 
OK, thank you very much, now I understand what's going on: In the current
directory is a Doxygen configuration file, which is executed. In this file
are some variables which are set to YES or NO. At some point this leads to
the execution of 'yes'...

Thank you for your time...

Christian Matuszewski

-- 
Weitersagen: GMX DSL-Flatrates mit Tempo-Garantie!
Ab 4,99 Euro/Monat: http://www.gmx.net/de/go/dsl

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