> > 2) In "configure.in", looks like that the configuration process will
> > issue the message "Parser was disabled" regardless of the
> > option that was passed to the "--enable-parser=...". Order of
> > commands there is wrong (in "configure.in", in the block
> > defining this behaviour ).
>
> I don't know. AC_ARG_ENABLE is sorta stupid: it takes a list of commands
> for when the flag is given on the command line, and one list of commands
> when the flag is not given on the command line. But it always calls the
> first list independent of whether --enable-parser or --disable-parser was
> given -- I actually don't know how exactly this is supposed to work, I
> find it very confusing and I don't know how one is supposed to distinguish
> between --enable-parser and --disable-parser.
>
Yes, but there is also a human mistake, look in the block
------------------------------------------------------------------
AC_ARG_ENABLE(parser,
AC_HELP_STRING([--enable-parser],
[While switched on by default, this option allows
to switch off support for the function parser
in the contrib directory.]),
[ enableparser=$enableval
(*) AC_MSG_RESULT(Function parser disabled)
if test "x$enableval" = "xno" ; then
AC_DEFINE(DEAL_II_DISABLE_PARSER,1,
[disable the function parser in contrib])
fi],
enableparser=yes)
AC_SUBST(enableparser)
AC_SUBST(DEAL_II_DISABLE_PARSER)
--------------------------------------------------
The line marked with (*) should be inside the "if" block that follows it.
for the cases "--enable-parser=yes" and "--enable-parser=anything_but_not_no"
Thank you, regards,
Dima.
_______________________________________________
