Here is the steps I followed in CodeBlocks IDE:
Create a new project->console->C->Name->debug and release->finish
So when I choose
main.c and build it, It should show the "Hello World!" ,But I get this weird
mingw32-gcc.exe: error: CreateProcess: No such file or directory error.
I've written and compiled about 20 C files this way, But I don't know what had recently happened to the IDE.
I've checked the CodeBlocks forum and googled this problem;No results
-------------- Build: Debug in C (compiler: GNU GCC Compiler)--------------- mingw32-gcc.exe -Wall -g -c "C:...\Project Files\C Codes\C\main.c" -o obj\Debug\main.o mingw32-gcc.exe: error: CreateProcess: No such file or directory Process terminated with status 1 (0 minutes, 0 seconds) 1 errors, 0 warnings (0 minutes, 0 seconds)
I've used CodeBlocks 10.02 three days ago and it compiled and runned a code successfully.It showed this error yesterday.I thought that maybe the code file isn't included so I removed the previous code from the project and added the new file(I do like this for about 20 codes and always get result); but the error still exists.Then I rebuilded the project but still got the error . I uninstalled ver.10.02 and installed a new version 12.11 today. Again I get this weird error
P.S. It looks like someone else have had this problem too:
mingw32-g++.exe: error: CreateProcess: No such file or directory
==>SOLVED: I ANSWERED MY QUSETION<==
Codeblocks seems to be calling gcc correct -- I'm not seeing anything wrong with the way it's being invoked. The error message you're getting:
gcc.exe: error: CreateProcess: No such file or directory
indicates that there is something wrong with your installation of mingw-gcc. Since you said that this was working previously, that likely means some files required for gcc to function are either corrupted, inadvertently renamed, moved elsewhere or accidentally deleted.
In fact, I was able to reproduce that exact error by renaming
cc1.exe. This is the C compiler that gcc needs to able to compile a C source file. On my install for Mingw-4.6.3, this resides under
./libexec/gcc/i686-w64-mingw32/4.6.3. Yours may be different depending on which mingw version and variant you're using.
I recommend downloading and reinstalling your copy of gcc altogether since fixing this manually can be tricky.