In some circumstances, it might be useful to alter the predefined compiler flags. An example might be when some new level of code optimization becomes available on your machine. Note that care should be exercised with code optimizers: we know of cases where the optimizers introduce real bugs into the code. As a consequence, it might be a good idea to turn optimization off before deciding that some strange behaviour of the package is anomalous and worth reporting. This is another reason why modifying compiler flags might be useful. Some operating system revisions might also require that you change machine dependent constants or procedures (such as the timer).
If compiler flags should be changed prior to a rebuild, the user should do so by altering the CompileCmd and LoadCmd variables corresponding to their compiler in the file $MYCUTER/config/system.cf or in $MYCUTER/config/all.cf.
If compiler flags should be changed to affect all subsequent installations of CUTEr, the user should do so in some or all the files $CUTER/config/system.cf, including $MYCUTER/config/all.cf.
For instance, if the compiler in question is only found on SUN machines, the file sun.cf should be modified. If it may be found on any machine, the file all.cf should be modified.