Code::Blocks

I have a problem trying to compile wxWidgets 2.6.1 with Code::Blocks/MinGW integrated package.I always get an error telling "gcc: installation problem, cannot exec 'cc1'What's wrong with my setup as I only installed C::B and MinGW together ?Thanks

I have the same problem. Googled a lot, but couldn't find a thing. Is there a way to find out where make is looking for cc1.exe? I guess it's simply looking in the wrong directory, because i found the cc1.exe file in C:\Program Files\CodeBlocks\libexec\gcc\mingw32\3.4.4.

E:\work\web\SDN\recipe-nddocs\cpp>Strage things are: use of internal specs and use of releative paths in search dirs.However specs is not really needed. At least cc1 will be called w/out them.But paths seems to be relevant.Do you have C:\Program Files\CodeBlocks\libexec\gcc\mingw32\3.4.4, C:\Program Files\CodeBlocks\lib\gcc\mingw32\3.4.4 and C:\Program Files\CodeBlocks\include\c++\3.4.4 directories?

It looks like gcc looks in your path for the bin directory where it resides and then uses relative paths from there to find programs and libraries. The only codeblocks or mingw stuff in my path isC:\MinGW\bin

Seems I understand what is going here.Make sure gcc.exe is not somewhere else in your %path% except C:\Program Files\CodeBlocks\binThe only way I can get this error is to copy single gcc.exe to some directory and call it from there.

I seem to remember that mingw32 should be installed to a directory that does not contain spaces in the path. I always avoid"Program Files" for this reason. I am not sure what symptoms are exhibited by incorrect installation or if this applies to the codeblocks install but try installing to C:\codeblocks or similar.

Do you have cygwin on your computer? In that case, it may be that you are actually invoking the wrong make. I once had that, took me three days to find out. This produces the exact same error message.

Apart from that, I always deem it a good idea to have MinGW installed in C:\mingw. Keep everything as simple and clear as possible (it gets complicated on its own).One installation, and only one. No complicated pathnames, no ambiguous stuff.

set path=C:\mingw;C:\mingw\mingw32 so there are no questions about your path, either. wxWidgets is still a hideous beast, and it can still fail to compile, but it is less likely if you have eliminated all the obvious troublemakers.