Discussion:
Documentation issues
Bruce Korb
2013-06-16 17:46:11 UTC
Permalink
Autoconf
********

This manual (24 April 2012) is for GNU Autoconf (version 2.69), a
package for creating scripts to configure source code packages using
templates and an M4 macro package.

Copyright (C) 1992-1996, 1998-2012 Free Software Foundation, Inc.
[...]
15.2 Working With External Software
===================================
[...]
AC_ARG_WITH([readline],
[AS_HELP_STRING([--with-readline], <<<=== invalid macro
[support fancy command line editing @<:@default=check@:>@])],
[],
[with_readline=check])

LIBREADLINE=
AS_IF([test "x$with_readline" != xno],
[AC_CHECK_LIB([readline], [main],
[AC_SUBST([LIBREADLINE], ["-lreadline -lncurses"])
AC_DEFINE([HAVE_LIBREADLINE], [1],
[Define if you have libreadline])
],
[if test "x$with_readline" != xcheck; then
AC_MSG_FAILURE(
[--with-readline was given, but test for readline failed])
fi
], -lncurses)]) <<<=== needs quoting


configure.ac:40: the top level
configure.ac:43: error: possibly undefined macro: AC_ART_WITH
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
configure.ac:44: error: possibly undefined macro: AS_HELP_STRING
Zack Weinberg
2013-06-16 19:44:29 UTC
Permalink
Post by Bruce Korb
[...]
15.2 Working With External Software
===================================
[...]
AC_ARG_WITH([readline],
...
Post by Bruce Korb
configure.ac:40: the top level
configure.ac:43: error: possibly undefined macro: AC_ART_WITH
Typo? AC_ARG_WITH, not AC_ART_WITH.

This might also explain the AS_HELP_STRING error.

zw
Bruce Korb
2013-06-16 20:53:30 UTC
Permalink
Post by Zack Weinberg
Typo? AC_ARG_WITH, not AC_ART_WITH.
This might also explain the AS_HELP_STRING error.
Must have been. I fixed them both at once (replacing that with
"AC_HELP_STRING", which seemed more correct). Now I see that
AS is preferred. I think it weird, but I'm sure there's a reason
somewhere....

Thanks.

Still the teeny quoting niggle. :)

Loading...