Code::Blocks Forums
User forums => Using Code::Blocks => Topic started by: Wahooney on July 15, 2007, 10:07:23 pm
-
Hey guys,
I'm having some serious problems with c::b and mingw32. As of this morning I haven't been able to build my projects created in c::b, which is odd since it was working 100% yesterday.
Firstly, I have read through the Installing MinGW on Vista article in the Wiki and although I'm having most of the same problems, I am actually running Windows XP.
Ok, firstl of all c::b started by reporting that it couldn't find cc1plus.exe, which I subsequently fixed by adding it's folder to Toolchain Executables > Additional Paths.
Then after that, on compile, I get the following error:
C:/MinGW/include/string.h:24:20: stddef.h: No such file or directory
I fix that by adding:
C:\MinGW\include\c++\3.4.5
C:\MinGW\include\c++\3.4.5\backward
C:\MinGW\include\c++\3.4.5\mingw32
C:\MinGW\lib\gcc\mingw32\3.4.5\include
to my Search directories > Complier.
Now, after that, on compiling, I get the following error:
ld: crt2.o: No such file: No such file or directory
Which is bizarre, because the path to that file is in my Search directories > Linker, C:\MinGW\lib.
I have a feeling that this is related to a windows update or something similar.
Has anyone else encountered a problem like this?
Thanks guys.
-
Normally you simply set Global compiler settings->Toolchain executables->Compiler's installation directory to point to your mingw installation and you are fine (be sure to use a current nightly build).
-
The compiler's installation directory is correct and it still doesn't work :cry:
Any other suggestions?
-
Please install MinGW runtime package.
http://downloads.sourceforge.net/mingw/mingw-runtime-3.12.tar.gz?modtime=1174904892&big_mirror=1
-
The runtime has been installed and I still get the same error:
I have crt2.o, in C:\MinGW\lib, and my Search directories > Linker has a path pointing to that folder too.
I just don't know...
-
What compiler logging do you use (Settings -> Compiler and debugger -> Tab: Other Settings -> Compiler Logging)? Choose Full command line and check in the Build log whether C::B is generating the right commands for invoking compiler and linker.
-
I was told that the Windows Malicious Software Removal Tool does random things to your PC and it can't be removed, so I formatted my PC and made a note of not installing it (not that I installed it in the first place thanks to MS Updates), but now it all seems to be working perfectly without the need to set those extra paths.
Thanks for the help guys.