Autoconf, Libtool, and an undefined AC_PROG_LIBTOOL

Update: Just use Homebrew to install these packages and move on with life.

Install Homebrew and just install the autoconf, automake and libtool packages like this:

brew install autoconf automake libtool

When I wrote this answer about 3+ years ago, it was to correct a previous answer that was outdated, link-only and vague in explanation. At that time I preferred to use raw source compilation on macOS for a task like this rather than a package manager like Homebrew because I simply found Homebrew and MacPorts to be a tad immature back then.

Now I use Homebrew (aka brew) on macOS as regularly as I use apt-get on Ubuntu and yum on CentOS. I would recommend avoiding compiling anything from raw source code on macOS unless you really have no choice.

Old answer content below for reference purposes.

---

I realize this question is about 3+ years old, but the accepted answer is a link only answer and that link is now dead. And the other answer is technically correct, but it still does not explain the actual hands-on process required to install the GNU versions of autoconf, automake and libtool in Mac OS X.

First, Xcode—since at least version 4.3 I believe—no longer includes the GNU versions of autoconf, automake and libtool. This doesn’t mean you can’t install GNU tools on your own. And here is how.

I’ve used this process on Mac OS X 10.6 (Snow Leopard), 10.7 (Lion), 10.8 (Mountain Lion) and 10.9 (Mavericks) without issue.

Install Xcode and Xcode command line tools.

The first prerequisite is to have Xcode installed along with the Xcode command line tools as well. Chances are if you need autoconf, automake and libtool installed, you already have Xcode and the command line tools installed, but just pointing that out for those who don’t have that setup yet.

Now, onto the show! Just note that version numbers of downloads are based on what is current (as of April 2015) and works well as of the time of this post. Adjust to other versions if you need to:

---

Install autoconf 2.69.

Set the working directory to your home directory:

cd

Get the source code and decompress it:

curl -O -L http://ftpmirror.gnu.org/autoconf/autoconf-2.69.tar.gz
tar -xzf autoconf-2.69.tar.gz

Go into the uncompressed source code directory:

cd autoconf-*

Run the configure script on the source code:

./configure

Now run make to compile it:

make

Now install it:

sudo make install

Check the newly installed autoconf version to confirm all went well:

autoconf --version

Response should be something like this:

autoconf 2.69

---

Install automake 1.15.

Set the working directory to your home directory:

cd

Get the source code and decompress it:

curl -O -L http://ftpmirror.gnu.org/automake/automake-1.15.tar.gz
tar -xzf automake-1.15.tar.gz

Go into the uncompressed source code directory:

cd automake-*

Run the configure script on the source code:

./configure

Now run make to compile it:

make

Now install it:

sudo make install

Check the newly installed automake version to confirm all went well:

automake --version

Response should be something like this:

automake 1.15

---

Install libtool 2.4.6.

Set the working directory to your home directory:

cd

Get the source code and decompress it:

curl -OL http://ftpmirror.gnu.org/libtool/libtool-2.4.6.tar.gz
tar -xzf libtool-2.4.6.tar.gz

Go into the uncompressed source code directory:

cd libtool-*

Run the configure script on the source code:

./configure

Now run make to compile it:

make

Now install it:

sudo make install

Check the newly installed libtool version—via the man page—to confirm all went well:

man libtool

On the first page of the man page there should be something like this:

libtool - manual page for libtool 2.4.6

Citing this:

• https://serverfault.com/questions/580489/configure-error-c-compiler-cannot-create-executables-while-build-ruby-from-sou

gcc -V is a way of selecting a specific gcc version when you have more than one, that's a decoy here though: configure is iterating through a set of options (--version -v -V etc.) to make sure it can log the version of the C compiler, be it gcc or something else.

Citing this:

• http://www.linuxquestions.org/questions/linux-newbie-8/slackware-configure-error-4175507097/#post5182892

gcc used to have a -V option for version reports. It now uses -v, and provides the configuration options used when the compiler was built.

You package is a bit dated and doesn't reflect that fact.

BTW, the -qversion option was merged into the -v...

Citing this:

• https://stackoverflow.com/questions/20678016/autoconf-complains-c-compiler-cannot-create-executables-on-linux-mint

On some versions of gcc, the -V option tells it to use a specified version of the compiler -- but it requires an argument. It's documented here. The option appears to have been removed some time between 4.5.4 and 4.6.4.

which references this:

• https://gcc.gnu.org/onlinedocs/gcc-4.1.2/gcc/Target-Options.html