http://invisible-island.net/
Copyright © 1997-2011,2013 by Thomas E. Dickey

Synopsis

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.

General Scripts

There are several general-purpose scripts:

archive.
Script to construct a gzip'd (or compress'd) tar file.
diff-patch.
A script that combines diffstat and makepatch.
exports
script to show which symbols are exports from object files
externs
display all external symbols from a collection of object files
make-out
run "make", redirecting output to make.out.
makepatch
script (originally by Johan Vromans) used for making patch-files. I have modified it to sort the old/new lists to avoid confusing '/' with filename stuff.
path
like which, but provides the dual use of showing the path and showing details about the arguments. The conflict program is related.
run-out
run a command, redirecting output to run.out.

Specific Scripts

Each program has its own set of build-scripts. Sample scripts for the larger programs are included in the download.

build-XXX

Build the program (within its working directory), with the most common configuration(s).

build-all-XXX

Repeat the build-XXX script for a given program, using different compilers and/or warning levels.

build-opt-XXX

Build a given program, use the options from the corresponding all-opts-XXX script, one at a time, to build the program.

clean-XXX

These remove the files from a build within the given program's working directory.

save-XXX

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.

Reporting Problems

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.

Download