Author Topic: Compiler problem  (Read 4187 times)

Figs

  • Guest
Compiler problem
« on: March 21, 2008, 10:48:33 am »
There's probably (hopefully!) a simple explanation for this, but I'm having trouble getting my compilers to play nicely with Code::Blocks. When I installed and ran Code::Blocks 8.02, it detected both versions of gcc I have installed (one with cygwin, and one with Mingw) without an problem... so, I go to compile a simple bit of code, and, hello! What's this? It can't find any of my include directories, Mingw files, etc. I went and searched around the folders for what I was missing and added it to the global compiler settings, but still get errors about a non-existent bits/c++config.h file in one of the standard libraries. After a bit of digging through the include folders, I find a file bits\c++config.h that seems to be what it's after; however, I've tried adding the directory containing the 'bits' subdir it's looking for, I've tried including the actual subdir itself, all to no avail -- it still refuses to acknowledge its existence as far as I can tell. (This is all with the gcc w/ Mingw version, btw)

I also tried to use the cygwin version, but that just gives me the cryptic error code '34304'.

Does anyone have any idea what's going on here? If it helps, I'm currently (unfortunately) running on Vista...

Offline Seronis

  • Almost regular
  • **
  • Posts: 197
Re: Compiler problem
« Reply #1 on: March 21, 2008, 01:32:13 pm »
On the download page there is a codeblocks installer that has a version of MinGW that is patched to play nicely with Vistas issues.  When you install that bundle there will be a  /mingw directory inside your C::B root directory.  Make sure this is the mingw that gets used.

chelah

  • Guest
Re: Compiler problem
« Reply #2 on: July 09, 2008, 03:54:15 am »
I also tried to use the cygwin version, but that just gives me the cryptic error code '34304'.

I had this problem on my first cygwin try. I thought maybe something in the startup script had cause this. So I clicked on 'Setting->Edit startup script'. Vista warned me that it could be malicious so I let Vista block it. And C::B reported I didn't have a startup script. I clicked on that menu again and for that time I allowed vista to execute the script. I closed C::B to restart and it said default had changed. So I just saved it. I restarted C::B and my problem solved. I didn't do anything with the script.