Dou you have g++ installed ?I just checked it, it is indeed a dependency, so please post the full error message from the build log, not tthe build messages.
I'm not sure it is a dependency of the build-essential package.
-------------- Build: Debug in testProject (compiler: GNU GCC Compiler)---------------
g++ -Wall -fexceptions -g -c /home/USER_NAME/Programing/testProject/main.cpp -o obj/Debug/main.o
/bin/bash: g++ -Wall -fexceptions -g -c /home/USER_NAME/Programming/testProject/main.cpp -o obj/Debug/main.o: No such file or directory
Process terminated with status 127 (0 minute(s), 0 second(s))
1 error(s), 0 warning(s) (0 minute(s), 0 second(s))
-------------- Build: Debug in testProject (compiler: GNU GCC Compiler)---------------
g++ -Wall -fexceptions -g -c /home/USER_NAME/Programing/testProject/main.cpp -o obj/Debug/main.o
/bin/sh: 0: Can't open g++ -Wall -fexceptions -g -c /home/USER_NAME/Programming/testProject/main.cpp -o obj/Debug/main.o
Process terminated with status 127 (0 minute(s), 0 second(s))
0 error(s), 0 warning(s) (0 minute(s), 0 second(s))
g++ (Ubuntu/Linaro 4.7.3-1ubuntu1) 4.7.3
g++ -Wall -fexceptions -g -c /home/USER_NAME/Programming/GDFFDF/main.cpp -o obj/Debug/main.o
/bin/bash: g++ -Wall -fexceptions -g -c /home/USER_NAME/Programming/GDFFDF/main.cpp -o obj/Debug/main.o: No such file or directory
If you are dual-booting with Windows, it is a good idea to use a Linux-formatted (ext3 or ext4) partition. I've had similar strange issues when compiling on an NTFS partition from Linux.
g++ -o program main.cpp
I went into Environment settings and tried changing "Shell to run commands with:" to /bin/bash. Here is the result after I clicked build.Code
-------------- Build: Debug in testProject (compiler: GNU GCC Compiler)---------------
g++ -Wall -fexceptions -g -c /home/USER_NAME/Programing/testProject/main.cpp -o obj/Debug/main.o
/bin/bash: g++ -Wall -fexceptions -g -c /home/USER_NAME/Programming/testProject/main.cpp -o obj/Debug/main.o: No such file or directory
Process terminated with status 127 (0 minute(s), 0 second(s))
1 error(s), 0 warning(s) (0 minute(s), 0 second(s))
Same thing happens with the default /bin/sh.Code
-------------- Build: Debug in testProject (compiler: GNU GCC Compiler)---------------
g++ -Wall -fexceptions -g -c /home/USER_NAME/Programing/testProject/main.cpp -o obj/Debug/main.o
/bin/sh: 0: Can't open g++ -Wall -fexceptions -g -c /home/USER_NAME/Programming/testProject/main.cpp -o obj/Debug/main.o
Process terminated with status 127 (0 minute(s), 0 second(s))
0 error(s), 0 warning(s) (0 minute(s), 0 second(s))
I tried clicking both Debug and Release, with both shell programs. Still shows this error message.
I went into Environment settings and tried changing "Shell to run commands with:" to /bin/bash. Here is the result after I clicked build.Code
-------------- Build: Debug in testProject (compiler: GNU GCC Compiler)---------------
g++ -Wall -fexceptions -g -c /home/USER_NAME/Programing/testProject/main.cpp -o obj/Debug/main.o
/bin/bash: g++ -Wall -fexceptions -g -c /home/USER_NAME/Programming/testProject/main.cpp -o obj/Debug/main.o: No such file or directory
Process terminated with status 127 (0 minute(s), 0 second(s))
1 error(s), 0 warning(s) (0 minute(s), 0 second(s))
Same thing happens with the default /bin/sh.Code
-------------- Build: Debug in testProject (compiler: GNU GCC Compiler)---------------
g++ -Wall -fexceptions -g -c /home/USER_NAME/Programing/testProject/main.cpp -o obj/Debug/main.o
/bin/sh: 0: Can't open g++ -Wall -fexceptions -g -c /home/USER_NAME/Programming/testProject/main.cpp -o obj/Debug/main.o
Process terminated with status 127 (0 minute(s), 0 second(s))
0 error(s), 0 warning(s) (0 minute(s), 0 second(s))
I tried clicking both Debug and Release, with both shell programs. Still shows this error message.
You see this message because path "obj/Debug/main.o" is invalid on Linux. You need to change your configuration to something like "./obj/Debug/main.o" or "/full/path/to/obj/Debug/main.o".
Don't do that or you get debug and release object files mixed and this might or might not work.
Try the exact same command from exact same folder (projects root folder), if that works, check the user that C::B really runs as and make sure no non-ascii characters are in the path (not even in username) given to the compiler or all discussion here is just a waste of time.
/bin/sh
/bin/sh -c
const wxString DEFAULT_CONSOLE_SHELL = _T("/bin/sh -c");
Looks like you guys have already resolved the issue and Jens's idea was correct. Good call.
So what's the conclusion? Everyone on Ubuntu and derivatives must go to environment settings and add "-c" or compile C::B from source?
The default (when created from scratch, e.g. by deleting the default.conf or using a different personality) is "/bin/sh -c".
The default is hardcoded in globals.cpp:58 as follows:CodeIf this is really not the default for the C::B from Ubuntu's repo, they must have changed it.const wxString DEFAULT_CONSOLE_SHELL = _T("/bin/sh -c");
In this case, please file a bug-report against the Ubuntu bug-tracker.