https://sourceware.org/bugzilla/show_bug.cgi?id=4356
--- Comment #26 from David Macek <david.macek.0 at gmail dot com> --- Sorry for the confusion, I stand corrected. I assumed the presented inconsistency, although in an incorrect usage, would translate into an inconsistency with correct usage. I tried directing windres to something like "C:\path with spaces\gcc", but I wasn't able to break it regardless of temp files. On the other hand, I was able to break windres by having it itself be in a path with spaces: $ mklink /j "W:\mingw64 root" "C:\msys64\mingw64" Junction created for W:\mingw64 root <<===>> C:\msys64\mingw64 $ set PATH=C:\windows\system32;W:\mingw64 root\bin $ "W:\mingw64 root\bin\windres.exe" a.rc -o a.res --use-temp-file W:\mingw64 root\bin\windres.exe: CreateProcess (null): No such file or directory $ "W:\mingw64 root\bin\windres.exe" a.rc -o a.res 'W:\mingw64' is not recognized as an internal or external command, operable program or batch file. W:\mingw64 root\bin\windres.exe: preprocessing failed. $ "W:\mingw64 root\bin\windres.exe" a.rc -o a.res "--preprocessor=W:\mingw64 root\bin\gcc" --preprocessor-arg=-E --preprocessor-arg=-xc (works) $ "W:\mingw64 root\bin\windres.exe" a.rc -o a.res "--preprocessor=W:\mingw64 root\bin\gcc" --preprocessor-arg=-E --preprocessor-arg=-xc --use-temp-file (works) -- You are receiving this mail because: You are on the CC list for the bug.
