Ethereal-dev: Re: [Ethereal-dev] Need tester with autoconf 2.13 (automake 1.7 patch)

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: Tue, 8 Oct 2002 19:27:02 -0700
On Wed, Oct 09, 2002 at 02:30:34AM +0200, Joerg Mayer wrote:
> Could you please use cvs + the attached patch instead? If this works
> I'll need to crosscheck with Didier whether it still works for him too.

It worked.

> Also, it looks like libtool is the problem this time. Which version are
> you using?

	% libtool --version
	ltmain.sh (GNU libtool) 1.3.4 (1.385.2.196 1999/12/07 21:47:57)

but there were, before the fatal libtool problem, non-fatal complaints
about "config.sub" (I think - it was one of the "config.*" files) not
having enough arguments passed to it, so there might be an underlying
problem (host not set) that caused both the config.sub problem and the
libtool problem.

BTW:

>  dnl Check for CPU / vendor / OS
> +AC_CANONICAL_HOST
>  AC_CANONICAL_TARGET

AC_CANONICAL_TARGET isn't documented in the autoconf 2.13 info file, and
the 2.13 source says it's "Internal use only." - it's used by
AC_CANONICAL_SYSTEM.

The info file says

 - Macro: AC_CANONICAL_SYSTEM
     Determine the system type and set output variables to the names of
     the canonical system types.  *Note System Type Variables::, for   
     details about the variables this macro sets.

 - Macro: AC_CANONICAL_HOST
     Perform only the subset of `AC_CANONICAL_SYSTEM' relevant to the
     host type.  This is all that is needed for programs that are not
     part of a compiler toolchain.

Is AC_CANONICAL_TARGET something documented by the new autoconf, or do
we have to do things that way in order to work with both the old and new
auto* stuff?  (Ethereal isn't, as far as I know, used by any compiler
toolchain. :-))