Copyright © 1997-2013,2014 by Thomas E. Dickey
These are some of the scripts that I use in configuring, building and saving the logfiles from building programs on multiple platforms. A complete set of configure- and make-logs is useful for bug reporting.
There are several general-purpose scripts:
which, but provides the dual use of showing the path and showing details about the arguments. The conflict program is related.
Each program has its own set of build-scripts. Sample scripts for the larger programs are included in the download.
Build the program (within its working directory), with the most common configuration(s).
build-XXX script for a given
program, using different compilers and/or warning levels.
Build a given program, use the options from the corresponding
all-opts-XXX script, one at a time, to
build the program.
These remove the files from a build within the given program's working directory.
I use these scripts to save logfiles after doing a build. They all assume that there is a parallel directory of the same name, e.g., ../save-vile, next to the current directory. The current directory is the top of the build tree.
In particular (making them useful for bug-reports), they save the results from the configure script, along with log-files that are created using the cfg-XXX and build-XXX scripts for the corresponding programs.
If you have a machine that I've not ported to, and have problems building one of the programs that I maintain, I will require the relevant information:
A uuencoded or mime'd gzip'd/tar file is preferred, because the logfiles can be awkward to email. Mailing uncompressed log-files also has the drawback that they may be rejected on mailing lists.