Re: build issues?

Robert Hart wrote:
> Did you try it more than once? I just did a completely fresh CVS pull,
> and got some of the errors that you got, but running ./autogen.sh a
> second time and they had gone.
> 
> Rob

ran it many times, but i'll pull a fresh one,   config.h doesn't seem to 
be created either.  I'll look at this again later today and really 
compare it against other projects that use the latest autoconf/automake 
and see if they're doing anything different because i've never had this 
problem before setting up a project.



> On Sun, 2003-10-05 at 01:37, Ed Sweetman wrote:
> 
>>Been a while since i tried compiling zinf, does nobody else use debian 
>>because for some reason autoconf is not understanding like anything from 
>>the config file anymore.  Even though the autogen.sh and configure.ac 
>>file look good.  It must be some aspect of the configure building prior 
>>to running autoconf.  I'm not familiar with autoconf at all.  This is a 
>>fresh cvs pull.
>>
>>
>>
>>Adding libtools.
>>You should add the contents of `/usr/share/aclocal/libtool.m4' to 
>>`aclocal.m4'.
>>Putting files in AC_CONFIG_AUX_DIR, `config'.
>>libtoolize: `config.guess' exists: use `--force' to overwrite
>>libtoolize: `config.sub' exists: use `--force' to overwrite
>>libtoolize: `ltmain.sh' exists: use `--force' to overwrite
>>Creating scripts/libchecks.m4
>>Building macros.
>>aclocal: configure.ac: 489: macro `AM_PATH_LIBXOSD' not found in library
>>Building config header.
>>Building makefiles.
>>configure.ac: no proper invocation of AM_INIT_AUTOMAKE was found.
>>configure.ac: You should verify that configure.ac invokes AM_INIT_AUTOMAKE,
>>configure.ac: that aclocal.m4 is present in the top-level directory,
>>configure.ac: and that aclocal.m4 was recently regenerated (using aclocal).
>>/usr/share/automake-1.7/am/depend2.am: am__fastdepCXX does not appear in 
>>AM_CONDITIONAL
>>/usr/share/automake-1.7/am/depend2.am: AMDEP does not appear in 
>>AM_CONDITIONAL
>>base/unix/Makefile.am:6: Libtool library used but `LIBTOOL' is undefined
>>base/unix/Makefile.am:6:
>>base/unix/Makefile.am:6: The usual way to define `LIBTOOL' is to add 
>>`AC_PROG_LIBTOOL'
>>
>>
>>-- Many more messages just like the one above for every makefile.
>>
>>Building configure.
>>configure.ac:23: error: possibly undefined macro: AM_INIT_AUTOMAKE
>>       If this token and others are legitimate, please use m4_pattern_allow.
>>       See the Autoconf documentation.
>>configure.ac:77: error: possibly undefined macro: AC_DISABLE_STATIC
>>configure.ac:78: error: possibly undefined macro: AC_PROG_LIBTOOL
>>configure.ac:83: error: possibly undefined macro: AM_GNU_GETTEXT
>>configure.ac:84: error: possibly undefined macro: AM_GNU_GETTEXT_VERSION
>>configure.ac:107: error: possibly undefined macro: AC_PROTOTYPE
>>configure.ac:145: error: possibly undefined macro: AC_ZINF_OS
>>configure.ac:182: error: possibly undefined macro: AM_WITH_PTHREAD_INFO
>>configure.ac:189: error: possibly undefined macro: AC_MSG_ERROR
>>configure.ac:212: error: possibly undefined macro: AM_ICONV
>>configure.ac:213: error: possibly undefined macro: AM_LANGINFO_CODESET
>>configure.ac:322: error: possibly undefined macro: AC_MSG_WARN
>>configure.ac:350: error: possibly undefined macro: AM_PATH_ALSA
>>configure.ac:368: error: possibly undefined macro: AM_PATH_ESD
>>configure.ac:454: error: possibly undefined macro: AM_PATH_GTK_2_0
>>configure.ac:473: error: possibly undefined macro: AM_PATH_ORBIT
>>configure.ac:489: error: possibly undefined macro: AM_PATH_LIBXOSD
>>
>>run "./configure ; make"
>>
>>



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf