Nope, but you can pass it a for "make.exe" valid path by using GetShortpathname first, silly
If it is too much trouble to pipe the paths through a little extra utility?
Help the whole toolchain to implement that then
Oh, well, I will. It's a 10 liner or something. (w/o too much housekeeping)
This is a Windows issue and I never understood why either symlink, hardlink, junction, SUBST to an alternative path without spaces /or GetShortPathName was ever used for the windows install. There is not really an excuse, but time. I might add that FPC has already the option to specify where to look for the binutils (-FD) so -FD<ShortPathName> solves the issue as well. Or setting the environment variable BINUTILSDIR probably...
These are all feasable options. Just tell me what is your favorite...