The standard user setup includes a bin directory in the home directory, and this is the usual place to add private scripts because it is already in your PATH. gcc can produce an output for a name you supply, -o test.out using your example.
#Code blocks no such file or directory how to
gcc by default rejects extensionless files, but steeldriver showed you how to override that (which is certainly not standard practice).Case is important, test.c is not test.C.c (I assumed setting the format to "C" in the editors would do that for me) Gcc: error: test.c: No such file or directoryĮdit2: I was being an idiot and not saving the files as. I also saved the files to the home directory and ran ls every time to make sure that they're there before attempting to compile.
The result was succesfull when using the gedit command, but unsuccesfull when creating the same file through an editor. c files I create through an editor, such as the default Ubuntu editor or Atom. I have build-essential installed and gcc seems to be functioning normally otherwise, what could be the cause of this? Help is much appreciated.Įdit: Upon further investigation, I've realised that this happens with. I am sure I'm using the command right (it's just a few letters, come on), but the compiler keeps complaining about there being "no such file or directory", regardless of what directory I try to compile from.
I just moved to Ubuntu and am currently learning C programming, so naturally I tried to compile some code.
0 kommentar(er)
