User forums > Help
gcc fails to build silently in code::blocks
trebor1718:
Hello,
I have created a new Project from the Template "Console application", Language C and GNU GCC Compiler.
In the new created Project when pressing the Compile Button I get this output in the Build log:
--- Code: ----------------- Build: Debug in RaspiTest (compiler: GNU GCC Compiler)---------------
gcc -Wall -g -fomit-frame-pointer -fexpensive-optimizations -Os -c /media/daten/AVR/R²/RaspiTest/code/main.c -o obj/Debug/main.o
g++ -o bin/Debug/RaspiTest obj/Debug/main.o -s
g++: error: obj/Debug/main.o: Datei oder Verzeichnis nicht gefunden
g++: fatal error: no input files
compilation terminated.
Process terminated with status 1 (0 minute(s), 0 second(s))
2 error(s), 0 warning(s) (0 minute(s), 0 second(s))
--- End code ---
When looking at obj/Debug the file main.o does not exist.
When running the commands manually in the console, everything works as expected though.
I tried with Code::Blocks 17.12 on Debian amd64, as well as with Raspbian on the Raspberry Pi.
Project attached as zip-file.
Thanks for your help.
Best regards
Robert
sodev:
The directory of the source file contains a non ascii character, CodeBlocks has trouble with these.
oBFusCATed:
What is the FS of /media/daten?
Having a source file in /tmp/R²/test works fine for me. :(
trebor1718:
moving to another path without the ² makes it work indeed, however other projects with avr-gcc or gcc for ARM work perfect in this path.
/media/daten has an xfs file system.
stahta01:
--- Quote from: trebor1718 on February 04, 2019, 09:50:01 pm ---moving to another path without the ² makes it work indeed, however other projects with avr-gcc or gcc for ARM work perfect in this path.
/media/daten has an xfs file system.
--- End quote ---
I am guessing the Compiler is different for these cases, correct?
Could be the compiler is having the problem with the path instead of Code::Blocks.
Tim S.
Navigation
[0] Message Index
[#] Next page
Go to full version