It seems to be something related to MinGW. I solved this exact issue by installing the TDM-GCC compiler version of Dev-C++ instead.
As it is, I've found it goes away after hitting any of the three buttons several times, then Dev-C++ loads. Its annoying, but Dev-C++ still works afterward. Its just a lot easier to not have to deal with the error message every time you load Dev-C++.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I can confirm what SilverNexus is saying. This is a problem related to MinGW-GCC 4.8.x.
To fix this problem, either use TDM-GCC or an older version of MinGW-GCC.
This bug in the compiler is being exposed by new functionality of Dev-C++ 5.6.x. As of this version, during startup the IDE will ask the compiler which preprocessor constants are hardcoded into the proprocessor. It does so this way (if cpp.exe is found):
GetCompilerOutput(BinaryDir,'cpp.exe','-dM -E -x c++ -std=gnu++11 NUL');
This should return a neat list of #defines, but on MinGW 4.8.x, it exposes a compiler bug. :(
Please note that I do NOT modify MinGW or TDM-GCC builds in any significant way when bundling them with Dev-C++.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It seems to be something related to MinGW. I solved this exact issue by installing the TDM-GCC compiler version of Dev-C++ instead.
As it is, I've found it goes away after hitting any of the three buttons several times, then Dev-C++ loads. Its annoying, but Dev-C++ still works afterward. Its just a lot easier to not have to deal with the error message every time you load Dev-C++.
I can confirm what SilverNexus is saying. This is a problem related to MinGW-GCC 4.8.x.
To fix this problem, either use TDM-GCC or an older version of MinGW-GCC.
This bug in the compiler is being exposed by new functionality of Dev-C++ 5.6.x. As of this version, during startup the IDE will ask the compiler which preprocessor constants are hardcoded into the proprocessor. It does so this way (if cpp.exe is found):
GetCompilerOutput(BinaryDir,'cpp.exe','-dM -E -x c++ -std=gnu++11 NUL');
This should return a neat list of #defines, but on MinGW 4.8.x, it exposes a compiler bug. :(
Please note that I do NOT modify MinGW or TDM-GCC builds in any significant way when bundling them with Dev-C++.