|
|
1.1 ! root 1: ___ In this directory, compilations need to be able to access "../compiler.h", "../machine.h", and "../defs.h". ! 2: The "makefile" specifies inclusion search path of "../". If "makefile" is not supported, or directory search ! 3: is not supported, you may have to physically copy each of these three header files into this directory. ! 4: ! 5: ___ In this directory, compilations need to be able to access "../util.o". ! 6: The "makefile" specifies the UTIL variable to be "../util.o". If "makefile" is not supported, or directory search ! 7: is not supported, you may have to physically copy the "util.o" file into this directory. ! 8: ! 9: ___ (If "makefile" is supported) Copy and/or modify one of the make* files into "makefile", with all local configurations ! 10: ! 11: ___ (If "makefile" is supported) Now execute make all which accomplishes the rest of the steps ! 12: listed on this page. If "makefile" is not supported, execute the rest of the steps listed on ! 13: this page, using "scripts", "batch files", or interactive execution. ! 14: ! 15: ___ For each "filename.c" file in this directory, compile it and link it with "../util.o" (capturing any compile errors in ! 16: a file "filename.z"), then execute it (directing its output onto the end of "filename.z"). ! 17: ! 18: ___ At this stage (or any other), if you have compiler errors that prevented the production of the ! 19: executable, you will need to find work-arounds, commenting-out, or "#if" exclusion to produce an ! 20: executable. ! 21: ! 22: ___ In this directory, however, the executables produced will not be needed for any further stages, so if ! 23: any particular compilation is hopelessly riddled with compile errors, you may simply note this fact, and ! 24: proceed further. ! 25: ! 26: ___ Catenate all of the "filename.z" files into one output file "all.out". This file will document any compiler bugs ! 27: which were revealed by the files in CONFORM/EXPRTEST. ! 28: ! 29: ___ This completes the installation of CONFORM/EXPRTEST.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.