adonthell-devel
[Top][All Lists]
Advanced

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

Re: [Adonthell-devel] mac os x port - success stories


From: Kai Sterker
Subject: Re: [Adonthell-devel] mac os x port - success stories
Date: Fri, 3 May 2002 10:22:24 +0200

On Thu, 2 May 2002 21:58:54 +0000 Nils Hesse wrote:

> Okay, never mind. I found a work around for this (I added 
> AC_CONFIG_HEADERS to the configure.in file). But now I'm back to the 
> macro problem I had with autogen...

First of all, I'm using automake 1.4 here. 

Perhaps, if you are running your autoconf from /sw then you should add
the contents of your /usr/share/aclocal to /sw/share/aclocal . Or vice
versa, depending where those auto- tools sit.

As far as the packages go that contain the macros:

> configure.in:13: error: possibly undefined macro: AM_INIT_AUTOMAKE
> configure.in:14: error: possibly undefined macro: AM_CONFIG_HEADER

automake

> configure.in:28: error: possibly undefined macro: AM_PROG_LIBTOOL

libtool (1.4.2)

> configure.in:36: error: possibly undefined macro: AM_GNU_GETTEXT

GNU gettext

> configure.in:111: error: possibly undefined macro: AM_PATH_SDL

SDL

> configure.in:120: error: possibly undefined macro: AC_CHECK_FT2

Freetype 2

> configure.in:130: error: possibly undefined macro: AM_PATH_VORBIS

libvorbis

> configure.in:145: error: possibly undefined macro: AM_PATH_PYTHON

is contained in our acinclude.m4

> configure.in:301: error: possibly undefined macro: AM_CONDITIONAL

automake

> configure.in:313: error: possibly undefined macro: AM_PATH_GTK

GTK 1.2


Hope that helps.

Kai



reply via email to

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