Description of problem:
Given a line in a config.h.in file that looks like
#undef SOME_SYMBOL /* some comment */
the new autoconf version transforms this to
/* #undef SOME_SYMBOL /* some comment */ */
which of course causes the C compiler to spit up.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. try to rebuild libjpeg in rawhide
Input of this form has worked properly since at least autoconf 2.13, so I claim this is a regression.
It's broken libjpeg and doubtless a few other packages too.
This might have worked wth older versions by pure luck, but upstream is aware of
problems with that and discourages putting comments on the same line as
from the autoconf info file:
4.9.1 Configuration Header Templates
The use of old form templates, with `#define' instead of `#undef' is
strongly discouraged. Similarly with old templates with comments on
the same line as the `#undef'. Anyway, putting comments in
preprocessor macros has never been a good idea.
It says that it's "discouraged", which is the same wording that's been there for awhile. If this change is
intentional, why doesn't it say "we intentionally broke this in 2.62"?
In the particular case I'm dealing with, the symbol in question is not one of the ones that autoconf has
been told to substitute, so I don't think it should be touching the line in the first place. Prior releases
reopening as suggested by the upstream developers in the discussion about this
A few nits in reply to comment #2:
> It says that it's "discouraged", [...]
The word "discouraged" is used for #define lines in the template, which have
been in use for a while indeed (late 1990's ?).
But comments on #undef template lines were never allowed.
> the symbol in question is not one of the ones that autoconf has been told to
substitute, so I don't think it should be touching the line in the first place.
Prior releases didn't...
This is pure coincidence; the remaining #undef lines in the template were always
But recent releases of autconf did not recognize this line, because of the
comment. OTOH, autoconf 2.13 did comment them out.
See how that thread will evolve for the upstream descussion. You are right that
the (syntactically wrong) "nested comment" is unfortunate, and you are right
that the documentation (yes, the node linked above) needs improvement. Thanks
for the bug report.
autoconf-2.62-3.fc10 with a fix for this issue will be in rawhide soon.