Re: Problem with FOR statements in command lines?

[Scott Bussinger]

> Could this be the result of a failure code getting
> back to gnumake from the shell because there are
> no files to enumerate?  That would explain why it
> works when files are present.  Try adding a minus prefix.

Sort of, that leads to:

    for %%a in (s\*.bak) do echo %%a
    gnumake: [default] Error 2883645 (ignored)

So it doesn't abort the make any longer, but it's pretty ugly none-the-less. 
It's not a matter of the errorlevel code being wrong though. If I run the 
commandline manually and then echo the errorlevel with

    echo %errorlevel%

it shows an errorlevel of 0, not the funny 2883645 number.

Be seeing you.