[Top][All Lists]

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

Re: [PATCHES] {maint} honour configure-time AUTOCONF and AUTOM4TE (was:

From: Stefano Lattarini
Subject: Re: [PATCHES] {maint} honour configure-time AUTOCONF and AUTOM4TE (was: Re: make check failures)
Date: Tue, 31 May 2011 00:13:03 +0200
User-agent: KMail/1.13.3 (Linux/2.6.30-2-686; KDE/4.4.4; i686; ; )

[re-adding automake list, as this mail might be of interest for its readers]

On Monday 30 May 2011, Graham Reitz wrote:
> Excellent.  Thanks again Stefano.
> I can clone the git depository directly.
> I saw a cvs link.   cvs -d :pserver:address@hidden:/automake.git \ checkout 
> -d automake HEAD
That's outdated, you should use the git repository directly if you can:

> What is the git url for the maint branch?
You can get the maint branch (which now contains my patches) with these

 $ git clone git://
 $ cd automake
 $ git checkout origin/maint
 $ git checkout -b maint

and than you should be able to build, test and install automake,
instructing it to use your custom autoconf installation in (say)
`/my/ac/path', by running:

 $ ./configure --prefix=... AUTOCONF=/my/ac/path/autoconf \
                            AUTOM4TE=/my/ac/path/autom4te \
                            AUTOHEADER=/my/ac/path/autoheader \
                            AUTOUPDATE=/my/ac/path/autoupdate \
 $ make all
 $ make check
 $ make install

from inside the cloned repository (you could also do a VPATH build
if you want, and that should work too; if it doesn't, that's a bug
in our build system).

Note that AUTOUPDATED, AUTOHEADER and AUTORECONF overrides are not
strictly needed to build and install automake, but they are used by
the testsuite, so that not specifying them could cause spurious
test failures.

> I'm more than happy to try things out and provide feedback if it
> helps you.  It's fun.
Thanks, this is really appreciated.

> graham


reply via email to

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