Version 4 (modified by andreasw, 13 years ago) (diff)

explicit warning to set AUTOTOOLS_DIR only for original GNU version

Using the Correct Version of the Autotools

We ask that every developer in COIN use the same version of the autotools. This is necessary in order to ensure that the custom defined COIN additions work. Also, this way we guarantee that each developer generates the same output files, which avoids the mess that would occur if this were not the case.

Since precompiled versions of the tools often differ (they may incorporate changes from the basic GNU release), we ask that you download the original source packages for the autotools from GNU and install them by hand on your system.

We recommend that you install the self-compiled tools in your $HOME directory, i.e., in $HOME/bin, and other configuration files in $HOME/share. This can be done by:

mkdir tmp
cd tmp
tar xvzf autoconf-2.59.tar.gz
cd autoconf-2.59
./configure --prefix=$HOME
make install
cd ..
tar xvzf automake-1.9.6.tar.gz
cd automake-1.9.6
./configure --prefix=$HOME
make install
cd ..
tar xvzf libtool-1.5.22.tar.gz
cd libtool-1.5.22
./configure --prefix=$HOME
make install
cd ../..
rm -fr tmp

Alternatively, you may install them (from the GNU source, not as binaries!!!) in another directory, (such as /usr/local), but then you will have to set the environment variable AUTOTOOLS_DIR to this directory in your shell's login file (e.g., ~/.bashrc or ~/.cshrc). Only do this, if you actually installed the autotools into that directory yourself from the GNU source code, otherwise you will encounter many conflicts!!!

The tools that you should install are:

  • autoconf (version 2.59)
  • automake (version 1.9.6)
  • libtool (version 1.5.22)

You need to install them in this order, and you should always specify the same argument to --prefix.

You can get the source code for each package from

Make sure you get the correct version for each tool, as indicated in the list above.

After they are installed, you also need to ensure that your $PATH variable is set so that your self-installed versions of the tools are the ones that are actually used.

When you run configure in your local copy with the --enable-maintainer-mode flag (which you should do as a developer), it will test to see if the above conditions are met and will fail if they are not met.