Akim Demaille <[EMAIL PROTECTED]> writes:
> It cannot have ever *properly* worked.
Did in 2.13, as I said.
> Pay attention that you're referring to the creation of config.h.in.
Yes.
> Maybe AC_DEFINE(`echo FOO`) used to be understood by autoheader, but
> it was a misfeature. In the general case, this cannot be done,
> hence it must never work :)
AC_DEFINE_UNQUOTED(`echo FOO`). Why can't it work? What happened in
2.13 was that you ended up with
cat << END
#undef `echo FOO`
END
in configure. I can't see a problem with this.
- Macro: AC_DEFINE_UNQUOTED (VARIABLE, [VALUE], [DESCRIPTION])
Like `AC_DEFINE', but three shell expansions are
performed--once--on VARIABLE and VALUE: variable expansion (`$'),
command substitution (``'), and backslash escaping (`\'). Single
and double quote characters in the value have no special meaning.
Use this macro instead of `AC_DEFINE' when VARIABLE or VALUE is a
shell variable. Examples:
AC_DEFINE_UNQUOTED(config_machfile, "$machfile")
AC_DEFINE_UNQUOTED(GETGROUPS_T, $ac_cv_type_getgroups)
AC_DEFINE_UNQUOTED($ac_tr_hdr)
If this can't ever work, perhaps this text from the *2.14a* manual
should be abolished. _UNQUOTED can't ever work.
> What is the problem you are trying to address here?
I want to do things with parameters to autoconf macros. Like
AC_CHECK_FUNCS(foo) defines HAVE_FOO, not HAVE_foo.
/Johan
