bash and make are trapped in an endless loop

Christian Matuszewski
Mon Jun 27 13:28:00 GMT 2005

> --- Ursprüngliche Nachricht ---
> Von: Eric Blake <>
> An: Christian Matuszewski <>
> Kopie:
> Betreff: Re: bash and make are trapped in an endless loop
> Datum: Mon, 27 Jun 2005 06:50:14 -0600
> 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:

Unsubscribe info:
Problem reports:

More information about the Cygwin mailing list