> The same for me (that's the default configuration from within Code::Blocks.
Ok, thanks.
> I now ran SysInternals filemon myself. It's definetly the linker from DMC that is being called on my machine. Did you run filemon
> already? What's the result? Why is the difference? Do you have another version on DMC (note the name of the ZIP-file I
> downloaded)?
I didn't run filemon because I can see from my firewall which program (including the path) is getting invoked. It is definitely the link.exe from the dm845c/dm/bin. I had the same DMC version as you, and only one version.
> I can only confirm what takeshimiya said as well: In my opinion it's always a bad idea to have a compiler system in a path with
> spaces. Especially that's the case with cross-platform compilers. Could you just try another folder without spaces?
I really didn't think this had anything to do with it, because the linker was getting invoked, but you guys have been great, so I tried it. As I suspected, big waste of time, it didn't change anything. If the right linker hadn't been getting invoked, that could have been a candidate, but since it was, the execution path couldn't be the issue.
And then I thought to myself, self, maybe it's something like the spaces in a path name. Not spaces, but something else objectionable. And not the path for DMC, but the target path.
And there it was: wxp/utilities/dev/c++/console1
When I changed the C++ folder name to CPP, it worked.
Now isn't that a stinker!?
The thread I pointed-to earlier on DMC's forums has been updated.
You guys rock. Thanks for the help, and for sticking with me. I hope I can return the favor some day.
Best Regards,
Israel, at quarter to 2:00 in the morning.