Hi,
On 12 Nov 2001, Akim Demaille wrote:
> | Forthermore I believe the definition of m4_car is wrong. If I test
> | m4_foreach with the example in the explanation in m4sugar.m4... :
> |
> | m4_define(a, 1)dnl
> | m4_define(b, 2)dnl
> | m4_define(c, 3)dnl
> | m4_foreach([f], m4_split([a (b c
It seems that the output of the command line used to invoke ./configure in
config.log does not quote multi-word tokens properly. This problem exists
in 2.52, so I did a CVS checkout of autoconf this morning (12 Nov 2001 --
2.52g) and the problem still exists.
This did work properly in the config
* autogen macros added
Bruce Korb's latest achievement in his autogen project resulted in some
fine macro pieces which I have added to an extra subcategorie in the
ac-archive sfnet-branch until it gets decided where to put them in the
gnu-branch. I did also add a crosslink to http://auto
| Hmm, well, better, but still...
| So, after some more tracing and fiddling with m4, I think the definition
| of m4_foreach in m4sugar.m4 is highly non-optimal. Currently it is:
|
| m4_define([m4_car], [$1])
| m4_define([_m4_foreach],
| [m4_if(m4_quote($2), [], [],
|[m4_define([$1], [m
Why does the current autoconf generated configure test for
compilability (usability) of a header file, before presence?
Naively it seems the opposite of testing would make more
sense?
Jens
