[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Right place for possible bug in mingw32-make
From: |
Eli Zaretskii |
Subject: |
Re: Right place for possible bug in mingw32-make |
Date: |
Mon, 19 Apr 2010 21:23:15 +0300 |
> Date: Mon, 19 Apr 2010 19:36:04 +0200
> From: Jeroen Cranendonk <address@hidden>
> CC: address@hidden
>
> >> "cat.exe" test.txt test.txt test.txt test.txt test.txt test.txt>>
> >> (27440 bytes in this example, for just the arguments).
> >> cat.exe in the same folder.
> >>
> >> Btw, the quotes around cat.exe seem to matter.
> >>
> > Yes, the quotes cause the shell to be invoked to handle the command,
> > instead of invoking cat.exe directly.
> >
> Ahh, interesting. Is there a way to not use quotes and handle spaces in
> folders gracefully?
The only way I know if is to use the 8+3 short aliases of the file
names ("dir /x" will show them).
> There is no sh.exe anywhere, it's a pretty minimal mingw install.
> Mayby with windows 7 cmd.exe they decided to allow longer arguments?
> And mayby that's not supported well in make-w32 since noone could test
> it before?
> OR mayby windows7 cmd.exe is broken, now that'd be fun :)
Maybe, I don't know. Try searching the Internet, or looking for
similar problems on MSDN.
> If XP will give a too long error anyways, I need to get back to the guy
> who writes the makefiles though, since this won't work there anyways.
Right. Such long command lines are non-portable.