> From: Juanma Barranquero <lekktu@gmai...>
> Date: Sat, 28 Jan 2012 13:15:21 +0100
> Cc: sthfrnth@gmai..., help-emacs-windows@gnu....
>
> C:\emacs\trunk\lisp> ..\..\echocmd.exe "*find*"
> `..\..\echocmd.exe "*find*"'
> 0: `..\..\echocmd.exe'
> 1: `find-cmd.el'
> 2: `find-cmd.elc'
> 3: `find-dired.el'
> 4: `find-dired.elc'
> 5: `find-file.el'
> 6: `find-file.elc'
> 7: `find-lisp.el'
> 8: `find-lisp.elc'
> 9: `finder-inf.el'
> 10: `finder.el'
> 11: `finder.elc'
>
> >  And what do you see if you type
> >
> >  echocmd *.c
>
> C:\emacs\trunk\src> ..\..\echocmd.exe *.c
> `..\..\echocmd.exe *.c'
> 0: `..\..\echocmd.exe'
> 1: `alloc.c'
> [... the rest of .c files in src/ ...]
> 113: `xterm.c'
>
> > and
> >
> >  echocmd "*.c"
>
> Same output.

So the problem does exist, it's just that I mistakenly thought it
would not glob "*.c" and leave the quotes, while in fact it does glob
even if the wildcard is quoted.

What if you build with -lmsvcr71 on the GCC command line?  Does the
resulting program works correctly then, in that "*.c" results in an
un-globbed *.c wind up in argv[1], whereas *.c without quotes results
in the list of *.c files in argv[]?