Ethereal-dev: Re: [Ethereal-dev] The need to run autogen (almost) every day.

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next
From: Guy Harris <gharris@xxxxxxxxx>
Date: Wed, 11 Sep 2002 12:07:01 -0700
On Wed, Sep 11, 2002 at 07:13:11PM +0200, Joerg Mayer wrote:
> I have tried to reproduce this but haven't had any success. In case
> you are able to reproduce it: Which versions of automake and autoconf
> are installed on that system?

 % automake --version
 automake (GNU automake) 1.4

 Copyright (C) 1999 Free Software Foundation, Inc.
 This is free software; see the source for copying conditions.  There is NO
 warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
 PURPOSE.

 Written by Tom Tromey <tromey@xxxxxxxxxx>
 % autoconf --version
 Autoconf version 2.13

(Yes, I know they're old.  No, I don't plan to upgrade them any time
soon.)

> Has autogen.sh been run beforehand?

No.

> If not - does running it change anything about the problem?

Yes, running autogen.sh causes a valid configure script to be built.

> Does aclocal.m4 contain the GTK...2 macros?

If I touch configure.in and run make, when the make fails (because the
newly-generated configure script gets the error I mentioned) and I check
aclocal.m4 afterwards, it doesn't contain the macros.

If I then run autogen.sh, when it finishes, aclocal.m4 *does* contain
the macros.

Note that autogen.sh does

    aclocal_missing="-I $topdir/aclocal-missing"
    aclocalinclude="$ACLOCAL_FLAGS $aclocal_flags $aclocal_missing";

whereas Makefile does not do anything similar, so that aclocal, when run
by the

	$(ACLOCAL_M4):  configure.in  acinclude.m4
		cd $(srcdir) && $(ACLOCAL) $(ACLOCAL_AMFLAGS)

rule in Makefile (as a result of configure.in being changed) does not
cause stuff to be read from the aclocal-missing directory.