>>>>> "Lars" == Lars Hecking <[EMAIL PROTECTED]> writes:
>> Hm, I might be over picky, but I would have answered no.
>> autoheader 2.13 is including all the paragraphs which are related
>> to something which is AC_DEFINE'd, which is not necessarily all the
>> content of acconfig.h.
Lars> What about AC_DEFINE_UNQUOTED? And, shouldn't autoheader check
Lars> aclocal.m4, too?
I meant the family AC_DEFINE, I'm keyboard lazy :)
>> I have a patch which I will submit for CVS Autoconf which includes
>> the whole localdir's acconfig.h into config.h.in: it simplifies
>> dramatically the code, and improves its robustness, IMHO.
Lars> I'll have to find a solution within configure.in for the time
I was talking of something related but different. If it doesn't work
for you, then you have a bug in your system IMHO. If 2.13 had such a
failure, it would be known.
We need more details. Where is your acconfig.h? If not in ., did you
pass -l to autoheader? When tracing with -x, can you see autoheader
handling your acconfig.h?
Lars> being, because I can't force all developers to apply this patch
Lars> (once it's in the CVS). Looks like the only solution that'll
Lars> work right now is testing cache variables in configure.in and
Lars> using explicit AC_DEFINEs.
I don't understand what you mean. Are you saying you have no problems
with AC_DEFINE but you have with AC_DEFINE_UNQUOTED? From the
implementation point of view, I can't see any reason for such a
difference in 2.13, both AC_DEFINE's are defined exactly the same way:
| define([AC_DEFINE], [#
| ifelse([$3],,[#
| @@@syms="$syms $1"@@@
| ], [#
| @@@verbatim="$verbatim
| /* $3 */
| #undef $1
| "@@@
| ])])
|
| define([AC_DEFINE_UNQUOTED], [#
| ifelse([$3],,[#
| @@@syms="$syms $1"@@@
| ], [#
| @@@verbatim="$verbatim
| /* $3 */
| #undef $1
| "@@@
| ])])
Akim
