[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: order to run autotools
From: |
Bob Rossi |
Subject: |
Re: order to run autotools |
Date: |
Tue, 23 Jan 2007 11:17:16 -0500 |
User-agent: |
Mutt/1.5.12-2006-07-14 |
On Tue, Jan 23, 2007 at 05:15:00PM +0100, Ralf Corsepius wrote:
> On Tue, 2007-01-23 at 10:59 -0500, Bob Rossi wrote:
> > Hi,
> >
> > I'm learning a lot about the autotools. I want to say thanks to the list
> > for teaching me so much!
> >
> > I have a quick question, I run the autotools in this order,
>
> With recent auto*tools, you should use autoreconf instead
I'm using recent tools. I should use autoreconf instead of autoconf even
if I'm autoconf'ing for the first time? I do this when I check out the
tree for the first time.
> > aclocal -I config
> > autoconf -f
> > autoheader
> > automake -a
> > when I do an out-of-tree configure it works fine, but when I do the make
> > I get,
> > cd ../cgdb && /bin/bash
> > /home/bob/rcs/svn/cgdb/cgdb.testsuite/cgdb/config/missing --run
> > autoheader
> >
> > Am I doing something wrong or is this expected?
> The former, the order is wrong. But unless you're using ancient
> auto*tools, you're better off using autoreconf.
What's the order supposed to be then?
> Besides this, there is a (AFAICT, yet undiscovered) bug somewhere, which
> occasionally triggers "seemingly spurious" autoheader runs.
I can reproduce this every time.
Bob Rossi