Products Support Documentation Download
Using "autoreconf"

Introduction

If you are getting this from a RDM package, there is no need to run autoreconf. You can skip the steps described here and go directly to README-unix-configure.txt. If you need to regenerate configure, any of the Makefile.in files, or any of the other files generated by autoreconf please, read on.

If you got the source directly from our Version Control System, please follow the steps in README-prebuild.pl (not included in any source or object package) before continuing with the description here.

Prerequisite

There is no specific prerequisite except for a working development environment if you are building RDM examples and tutorials using an object package or building RDM using a source distribution. Please skip the rest of this file and continue with README-unix-configure.txt.

Make sure you have the versions (a newer version is not guaranteed to work) of the GNU Autotools installed as shown below. M4 must be a GNU version, and it can be an older version. For the other tools, make sure that you use versions that are known to work together.

If your package manager includes older versions, we recommended that you build these tools directly from source and install them. Please see the next section for details.

You can run these commands to check the versions of the tools you have:

$ autoconf --version
autoconf (GNU Autoconf) 2.68
$ libtool --version
libtool (GNU libtool) 2.4.2
$ automake --version
automake (GNU automake) 1.11.3
$ m4 --version
m4 (GNU M4) 1.4.16

Broken Autoconf on OS X

On OS X, these tools are currently known to be broken. The development tools as shipped by Apple come with a version of autoconf that does not work with the other tools. Download, compile, and install the GNU versions of the tools in a location where they are guaranteed to be found before the tools provided by Apple:

$ INSTALL=/usr/local
$ PATH="$INSTALL/bin:$PATH"

$ wget ftp://ftp.gnu.org/pub/gnu/autoconf/autoconf-2.68.tar.gz
$ tar xfz autoconf-2.68.tar.gz
$ cd autoconf-2.68
$ ./configure "--prefix=$INSTALL"
$ make
$ sudo make install
$ cd ..

$ wget ftp://ftp.gnu.org/pub/gnu/libtool/libtool-2.4.2.tar.gz
$ tar xfz libtool-2.4.2.tar.gz
$ cd libtool-2.4.2
$ ./configure "--prefix=$INSTALL"
$ make
$ sudo make install
$ cd ..

$ wget ftp://ftp.gnu.org/pub/gnu/automake/automake-1.11.3.tar.gz
$ tar xfz automake-1.11.3
$ cd automake-1.11.3
$ ./configure "--prefix=$INSTALL"
$ make
$ sudo make install
$ cd ..

Autoreconf

Make sure that you have the prerequisite listed in the first section installed. The GNU Autotools can be used on most systems where a resent version of the GNU Autotools have been installed. The output of this step is a set of scripts and Makefile template that can be used on any Posix system. Those systems do not rely on any Gnu specific tool. The GNU Autotools files can be set up running autoreconf:

$ autoreconf --install --force

The –install option will add some additional files needed for the configure script. This option can be omitted if you previously added those files. The –force option will overwrite these files with a clean copy. You will want to use this option if you upgraded your GNU Autotools installation.

Next Step

When the GNU build system has been set up using autoreconf, the next step is to configure a build environment as described in README-unix-configure.

Additional Help

Additional help can be found here:

http://www.gnu.org/software/autoconf http://www.gnu.org/software/automake http://www.gnu.org/software/libtool http://www.gnu.org/software/m4