User forums > Using Code::Blocks
no compiler program set
hanshuckebein:
My reply was partially wrong, sorry.
There is a notice on the toolchain executables tab:
NOTE: All programs must exist either in the "bin" sub-directory of this path, or in any of the "Additional paths".
So /usr should work - but it doesn't. I still get the error message:
Skipping file (no compiler program set): main.c
Until now I only used avr-gcc with CB using the avr-plugin. That works very well w/o any additional setup.
How to get CB running gcc on a linux system?
BlueHazzard:
--- Quote ---How to get CB running gcc on a linux system?
--- End quote ---
Normally it runs out of the box... You seem to have something strange on your system...
Can you make a screenshot of the compiler settings for gcc (Settings->Compiler->Global compiler settings->Select: "GNU GCC compiler" from the dropdown->Toolchain executable)?
If not: have you set the compiler names in the Settings->Compiler->Global compiler settings->Select: "GNU GCC compiler" from the dropdown->Toolchain executable->C compiler ecc..?
Can you try to generate a new project? After you have started codeblocks the first time?
--- Quote ---So /usr should work - but it doesn't. I still get the error message:
--- End quote ---
Have you tried the following paths:
--- Quote ---/usr/bin
/usr
--- End quote ---
?
Please restart codeblocks after changing the settings and try to create a new project, do not use the old project.
--- Quote from: hanshuckebein on January 03, 2019, 02:43:54 pm ---
--- Quote from: BlueHazzard on January 03, 2019, 02:29:24 pm ---
--- Quote from: hanshuckebein on January 03, 2019, 02:04:25 pm ---Very wise advice…
--- End quote ---
Well you did not give any information if you have installed any compiler, or if yes, what compiler do you have installed. So my first advise is to install a compiler...
If you have installed a compiler then say so and also give version and installation method...
remember codeblocks IS NOT A COMPILER, codeblocks is an IDE
--- End quote ---
Read my initial posting…
--- End quote ---
I did not see any answer to my questions in your first post...
hanshuckebein:
--- Quote from: BlueHazzard on January 03, 2019, 08:10:59 pm ---Normally it runs out of the box... You seem to have something strange on your system...
--- End quote ---
That's what I read and hoped.
--- Quote ---Can you make a screenshot of the compiler settings for gcc (Settings->Compiler->Global compiler settings->Select: "GNU GCC compiler" from the dropdown->Toolchain executable)?
--- End quote ---
See the attachments.
--- Quote ---Can you try to generate a new project? After you have started codeblocks the first time?
--- End quote ---
CB is running for years now on my system. (Usually w/ avr-gcc.) The gcc project is brand new.
--- Quote ---Please restart codeblocks after changing the settings and try to create a new project, do not use the old project.
--- End quote ---
I restarted after autodetect and a few moments ago started once more - no change. CB doesn't find gcc.
Few minutes ago, I generated a new test project and started gcc on the generated main.c - same effect, same error diagnostic.
--- Quote ---Well you did not give any information if you have installed any compiler, or if yes, what compiler do you have installed. So my first advise is to install a compiler...
--- End quote ---
See my posting from 02:43:54 pm. On most linux systems and specially on debian like systems, gcc is preinstalled. Linux Mint is such a system. And for sure the compiler works, I frequently use it to compile new packages from source downloads.
--- Quote ---If you have installed a compiler then say so and also give version and installation method...
--- End quote ---
See my posting from 02:43:54 pm - there is the complete version info of the compiler.
hanshuckebein:
Even directly selecting of gcc under toolchain executables dosn't help. Something is going badly wrong…
Is there a possibility to see the spawned command for gcc, issued by cb?
BlueHazzard:
--- Quote ---Is there a possibility to see the spawned command for gcc, issued by cb?
--- End quote ---
You can look in the "build log" tab of the message window. But i do not think that there is something logged. This message tells us that your compiler command is empty and the build process won't start with an empty command...
Can you try to rename your config file to something else and restart codeblocks? It should be located in your home folder in the sub folder .codeblocks and named default.conf (i do not remember where it is located on linux, it can also be in .config folder...) This will reset codeblocks to defaults.
If this is working can you zip the file and upload it?
avr gcc is working with exactly this installation?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version