##########################################################################
This is the most I know about compile from source code.
This was copied from a C pgm I got to count pages.

compile
                gcc test.c -o (path to)/cgi-bin/test.html
                        OR
                cc test.c -o (path to)/cgi-bin/test.html

gcc(GNU_C_compiler)test.c(file to compile) 
	 -o file
              Place  output  in  file  file.  This applies regardless to
              whatever sort of output GCC is producing, whether it be an
              executable file, an object file, an assembler file or pre-
              processed C code.
(path to the exec file that you just compiled)/test.html




Suffixes of source file names indicate the language and  kind  of
       processing to be done:

       .c    C source; preprocess, compile, assemble
       .C    C++ source; preprocess, compile, assemble
       .cc   C++ source; preprocess, compile, assemble
       .cxx  C++ source; preprocess, compile, assemble
       .m    Objective-C source; preprocess, compile, assemble
       .i    preprocessed C; compile, assemble
       .ii   preprocessed C++; compile, assemble
       .s    Assembler source; assemble
       .S    Assembler source; preprocess, assemble
	.h    Preprocessor file; not usually named on command line

       Files with other suffixes are passed to the linker.  Common cases
       include:

       .o    Object file
       .a    Archive file