On Mon, Jul 02, 2001 at 11:21:11AM +0300, Peter Pentchev wrote:
> On Mon, Jul 02, 2001 at 08:30:35AM +0200, Nicolas Souchu wrote:
> > Hi,
> >
> > The 2.13_1 complains about this:
> >
> > ladoga:/usr/home/admin/nsouch/ggi-core/libgii>autoconf
> > configure.in:157: warning: AC_TRY_RUN called without default to allow cross
>compiling
> > autoconf: Undefined macros:
> > configure.in:247:AC_CHECK_WINFUNCS(gettimeofday strdup nanosleep usleep _exit \
> > configure.in:39:AC_LIBTOOL_DLOPEN
> > configure.in:40:AC_LIBTOOL_WIN32_DLL
> > ladoga:/usr/home/admin/nsouch/ggi-core/libgii>
> >
> > And autoconf-2.50 gives me:
> >
> > ladoga:/home/admin/nsouch/ggi-core/libgii>autoconf
> > configure.in:8: error: possibly undefined macro: AM_INIT_AUTOMAKE
> > configure.in:10: error: possibly undefined macro: AM_MAINTAINER_MODE
> > configure.in:11: error: possibly undefined macro: AM_DISABLE_STATIC
> > configure.in:39: error: possibly undefined macro: AC_LIBTOOL_DLOPEN
> > configure.in:40: error: possibly undefined macro: AC_LIBTOOL_WIN32_DLL
> > configure.in:41: error: possibly undefined macro: AM_PROG_LIBTOOL
> > configure.in:247: error: possibly undefined macro: AC_CHECK_WINFUNCS
> > configure.in:397: error: possibly undefined macro: AM_CONDITIONAL
> > configure.in:665: error: possibly undefined macro: AM_CONFIG_HEADER
> >
> > Do you have any clue?
>
> Have you tried this with a newer automake, too? AFAIK, the newer
Newer than 2.50?
> versions of autoconf and automake are totally in-backwards-compatible :(
So the 2.13_1 version seems to be the closest to my configure.in file.
Then, could it be some missing macros in the FreeBSD installation?
Nicholas
--
Alcôve Technical Manager - [EMAIL PROTECTED] - http://www.alcove.com
Open Source Software Developer - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
