The macros are definitely used, and Thrift will not build if those types are unavailable. I'm not really sure what a "possibly undefined" macro is. Please feel free to add Lex, Yacc, and Sun Java to the requirements in the Wiki (though I suspect that other Java compilers will work as well).
--David Stanislav Sinyagin wrote: > [EMAIL PROTECTED] thrift.svn]# ./bootstrap.sh > configure.ac:31: error: possibly undefined macro: AC_PROG_MKDIR_P > If this token and others are legitimate, please use m4_pattern_allow. > See the Autoconf documentation. > configure.ac:101: error: possibly undefined macro: AC_TYPE_INT16_T > configure.ac:102: error: possibly undefined macro: AC_TYPE_INT32_T > configure.ac:103: error: possibly undefined macro: AC_TYPE_INT64_T > configure.ac:104: error: possibly undefined macro: AC_TYPE_INT8_T > configure.ac:108: error: possibly undefined macro: AC_TYPE_SSIZE_T > configure.ac:109: error: possibly undefined macro: AC_TYPE_UINT16_T > configure.ac:110: error: possibly undefined macro: AC_TYPE_UINT32_T > configure.ac:111: error: possibly undefined macro: AC_TYPE_UINT64_T > configure.ac:112: error: possibly undefined macro: AC_TYPE_UINT8_T > configure.ac: installing `./install-sh' > configure.ac: installing `./missing' > compiler/cpp/Makefile.am: installing `./depcomp' > > > If those macros are not in use, maybe it's worth removing them from > autoconf.ac? > > > > > > ----- Original Message ---- >> From: David Reiss <[EMAIL PROTECTED]> >> To: [email protected] >> Sent: Friday, September 5, 2008 12:51:05 AM >> Subject: Re: autconf dependency and dist snapshot >> >> I just built on CentOS without trouble. There were a lot of >> error messages from autoconf, but it appeared to work anyway. >> I've updated the wiki to reflect this. >> >> --David >> >> Stanislav Sinyagin wrote: >> > hi all, >> > >> > I'm excited to find your project, and I'm thinking to use >> > Thrift for my new development initiative. >> > >> > There's one problem though: Thrift snapshot requires autoconf-2.60 >> > or higher, and my development machine is CentOS 5.0, which does not have >> > an easy option for newer autoconf. I think that's not the only OS >> > distribution suffering from this. >> > >> > The easy way to ease the early users' life is to publish the result of >> > "make dist", instead of just the SVN snapshot tarball. >> > >> > The hard way would be to remove 2.60 dependency and make it compatible >> > with autoconf-2.59. >> > >> > By the way, in configure.ac you've got AC_PREREQ(2.59). >> > >> > The project in my mind is a new generation of Torrus > (http://torrus.org/). >> > The design goals and early requirements are described in >> > http://torrus.org/Torrus_2.0_Design_Concept.pdf >> > >> > cheers, >> > stan >> > >
