automake
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How to use alternative autoconf than what is located in /usr/local/b


From: Daniel Herring
Subject: Re: How to use alternative autoconf than what is located in /usr/local/bin (for automake compile)?
Date: Mon, 23 May 2011 21:48:31 -0400 (EDT)
User-agent: Alpine 2.00 (LNX 1167 2008-08-23)

On Mon, 23 May 2011, Daniel Herring wrote:

FYI, when I install a new version of the autotools, I do something like

# PATH=/new/path/bin:$PATH
# cd m4; ./configure --prefix=/new/path; make; make install
# cd ../autoconf; ./configure --prefix=/new/path; make; make install
# cd ../automake; ./configure --prefix=/new/path; make; make install
# cd ../libtool; ./configure --prefix=/new/path $OSXOPTS; make; make install

Oh, one other detail. It is often a good idea to tell the new aclocal where to find m4 files installed in the normal locations. This involves creating a dirlist file.

http://www.gnu.org/s/hello/manual/automake/Macro-Search-Path.html


The proper versions of everything are found because they are first in PATH.

The OSXOPTS for libtool is needed because Apple ships another program named libtool. GNU libtool is renamed to glibtool (IIRC). There are a couple ways of effecting this. IIRC, I use a setting that prefixes the program with a g (something like --program-prefix=g).

Later,
Daniel



reply via email to

[Prev in Thread] Current Thread [Next in Thread]