Mail Archives: djgpp/1999/09/30/12:58:42
On Wed, 29 Sep 1999, Rodeo Red wrote:
> Compiling: hello.cpp
> Bad command or file name
> no errors
> Creating: hello2.exe
> no errors
>
> If there are no errors, why does it say
> Bad command or file name
> in the second line ? .
"No errors" means the compiler exited with a zero exit code. The "Bad
command or file name" message means some installation problem: the
compiler cannot find some program it needs to run. To see what program
that is, add -v to the compilation switches that RHIDE passes to the
compiler. The program which GCC invokes immediately before "Bad command"
is printed is the one you should look for.
- Raw text -