I'm working without Cygwin, which I think is a valid use case.
I find that I can no longer replicate the problem with the top-level directory name from the archive file. I can also execute from paths with spaces so long as I do an explicit invocation with the full path to gcc. However, if I pick gcc up via the PATH environment variable, and gcc is in a path with a space, it fails.
i.e. this works:
C:\>"C:\has space2\gcc-linaro-arm-linux-gnueabi-2012.01-20120112+bzr2331~win32\b
in"\arm-linux-gnueabi-gcc H:\work\code\hello.c
I've just downloaded from http:// people. linaro. org/~michaelh/ incoming/ binaries/ to be sure I've got the latest.
I'm working without Cygwin, which I think is a valid use case.
I find that I can no longer replicate the problem with the top-level directory name from the archive file. I can also execute from paths with spaces so long as I do an explicit invocation with the full path to gcc. However, if I pick gcc up via the PATH environment variable, and gcc is in a path with a space, it fails.
i.e. this works: gcc-linaro- arm-linux- gnueabi- 2012.01- 20120112+ bzr2331~ win32\b linux-gnueabi- gcc H:\work\ code\hello. c
C:\>"C:\has space2\
in"\arm-
and this does not:
C:\>set PATH="C:\has space2\ gcc-linaro- arm-linux- gnueabi- 2012.01- 20120112+ bzr233
1~win32\bin";%PATH%
C:\>arm- linux-gnueabi- gcc H:\work\ code\hello. c gnueabi- gcc: error: CreateProcess: No such file or directory
arm-linux-