I have started with a empty file each time and the clean is greyed out in the build menu either with a fresh build or when I open one I saved?
The proper use of codeblocks is not to use only files, but to use projects... I don't know if the clean and build steps work with a single file (i would suggest to even deactivate the compile button unless a project is loaded....)
So, the proper utilization of c::b is to create a project and add your c files there. Then you should be able to make a clean rebuild...
OT (i write this here, so i can link to this answer from other questions, because it gets asked a lot):
You may ask why c::b does needs a project, even if you only want to use one file? Well, if you only want to use one file, why do you need a IDE anyway
? Simply use the command line and you are way faster... Codeblocks stores a lot information in the project, like compiler options, layout settings, dependency, debugger settings and so on. As soon as you are going to debug your application you need the project file. It is not really a problem to create a project instead of a cpp file (the wizard will do all the work for you), simply go File->New->Project, choose "console Application" and follow the shown steps....
I know you are trying to help but that did not help, I don't know where the build log is if it is not in the tab as that is what the FAQ sheet you pointed me asked for
or where to find the compiler version
There are two build information tabs in the log view: The "build messages" and the "Build log".
- build messages: are a shortened version of the Build log. This is the normal place where you find your compiler errors. Double click on one error and the editor will jump to the error line in your files
- Build log: This is the output from codeblocks to the compiler (and linker) and back. Here a more advanced user finds all details about the build process. To help you we need all compiler flags, your include directories and so on and this all is written in the project file, but also, and more compact, with response from the compiler in the "build log". If you post in this forum we only (but mandatory) need the build log (and your problem description )...
where to find the compiler version
This is quite tricky to get from within c::b (we should provide some info tab, where this is written, or incorporate it in the build log...) The easiest way to get it is from the command line:
Start->Run->cmd.exe->enter
then a black window will pop up. There you have to enter "gcc -v" without quotes and post the output..
greetings