autoconf: Transformation Examples

1 
1 15.7.2 Transformation Examples
1 ------------------------------
1 
1 These transformations are useful with programs that can be part of a
1 cross-compilation development environment.  For example, a
1 cross-assembler running on a Sun 4 configured with
1 `--target=i960-vxworks' is normally installed as `i960-vxworks-as',
1 rather than `as', which could be confused with a native Sun 4 assembler.
1 
1    You can force a program name to begin with `g', if you don't want
1 GNU programs installed on your system to shadow other programs with the
1 same name.  For example, if you configure GNU `diff' with
1 `--program-prefix=g', then when you run `make install' it is installed
1 as `/usr/local/bin/gdiff'.
1 
1    As a more sophisticated example, you could use
1 
1      --program-transform-name='s/^/g/; s/^gg/g/; s/^gless/less/'
1    to prepend `g' to most of the program names in a source tree,
1 excepting those like `gdb' that already have one and those like `less'
1 and `lesskey' that aren't GNU programs.  (That is assuming that you
1 have a source tree containing those programs that is set up to use this
1 feature.)
1 
1    One way to install multiple versions of some programs simultaneously
1 is to append a version number to the name of one or both.  For example,
1 if you want to keep Autoconf version 1 around for awhile, you can
1 configure Autoconf version 2 using `--program-suffix=2' to install the
1 programs as `/usr/local/bin/autoconf2', `/usr/local/bin/autoheader2',
1 etc.  Nevertheless, pay attention that only the binaries are renamed,
1 therefore you'd have problems with the library files which might
1 overlap.
1