autoconf (was [PATCH] memcached on FreeBSD...)

[Sean Chittenden]

> > http://premk.sourceforge.net/
> 
> The autotools have a lot of inertia, especially because they support
> platforms we've never even seen...

Bah, by that argument, use Win32.

> > > Try "automake --add-missing".  I suppose that's not in the autogen
> > > script, but it ought to be.
> > 
> > Duh, thanks, that helps some, but now I'm getting a syntax error in
> > configure:
> 
> Hm, wait.  The autogen script *does* include --add-missing.  Are you not
> running autogen for some reason?

...  oh, hey, that's handy (modifies it for BSD's naming convention).
I wasn't running autoheader. *sigh*

> > ./configure: line 1318: syntax error near unexpected token `memcached,'
> > ./configure: line 1318: `AM_INIT_AUTOMAKE(memcached, 1.1.9-snapshot)'
> > 
> > or with autoconf257:
> > 
> > ./configure: line 1393: syntax error near unexpected token `memcached,'
> > ./configure: line 1393: `AM_INIT_AUTOMAKE(memcached, 1.1.9-snapshot)'
> > 
> > autoconf can't find the macro AM_INIT_AUTOMAKE.  :-/
> > 
> > configure.ac:5: error: possibly undefined macro: AM_INIT_AUTOMAKE
> >       If this token and others are legitimate, please use m4_pattern_allow.
> >       See the Autoconf documentation.
> 
> Because m4 is a macro language, the errors are often very
> misleading.  Even though configure is failing, it could be any tool
> in the chain.  If AM_INIT_AUTOMAKE is undefined, it's likely
> something isn't providing it, and I'd suspect automake over
> autoconf.

*nods* 'tis be why I like pmk: less obtuse msgs.

Thanks for the help.

-sc

-- 
Sean Chittenden