StackThreads/MP: version 0.77 User's Guide

11.3: Compilation fails

Q: Compilation fails. Why?

A: stgcc simply calls gcc without any preprocessing. Therefore it virtually never happens that whatever errors gcc generated is caused by stgcc. Be sure that your program compiles with gcc.

There are still possibility that a program that successfully compiles with gcc does not successfully compile with stgcc.

• Environment variables: You have not set correct environment variables. You must define ST_DIR, ST_CPU_TYPE, ST_OS_TYPE, and ST_THREAD_PKG. See Installation for details.
• Path: You must make sure your PATH environment variable contains $ST_DIR/bin.
• Command line errors: Some options that are normally accepted by gcc are prohibited in stgcc. When stgcc detects such an error, it displays an error message and does not call gcc. See STGCC and STGPP A Wrapper for GCC for the list of prohibited options.
• GNU awk: Make sure you have gawk.
• Postprocessing errors: stgcc calls gcc to generate assembly and postprocesses generated code. There may be errors (that I do not know of at this moment) in this process. When it happens, it displays a simple diagnostic message (that is useful at least for me :-) and aborts compilation. This is a bug of the postprocessor. When it happens, please send the assembly program before postprocessing and what did the postprocessor say. To obtain the assembly program before postprocessing, give --dbg flag to stgcc. It generates, among other things, .t file. Send it to me (see STGCC and STGPP A Wrapper for GCC for command line options of stgcc. See Reporting Bugs for how to report bugs).

  The coding principle of the postprocessor is ``never go a wrong way,'' meaning that it stops whenever it encounters something unfamiliar. It assumes a stereotyped code generation of gcc and aborts when it finds anything unexpected.