https://gcc.gnu.org/bugzilla/show_bug.cgi?id=45433
Bruno Haible <bruno at clisp dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bruno at clisp dot org --- Comment #3 from Bruno Haible <bruno at clisp dot org> --- (In reply to Jakub Jelinek from comment #2) > You need to read the documentation, which would tell you you need to use > -fmain=HelloWorld option. It is true that -fmain=HelloWorld was missing in the reporter's command line. But if that had been the only problem, the error message would have been (.text+0x18): undefined reference to `main' not Exception in thread "main" java.lang.NoClassDefFoundError: org.eclipse.jdt.internal.compiler.batch.GCCMain The error message "java.lang.NoClassDefFoundError: org.eclipse.jdt.internal.compiler.batch.GCCMain" means that the ecj1 program cannot find the org.eclipse.jdt.internal.compiler.batch.GCCMain class, which it expects to find in the jar file specified through the --with-ecj-jar option. So, the reporter's real problem was that he configured GCC with a --with-ecj-jar option without argument.