Follow-up Comment #3, sr #110400 (project autoconf):
AC_LANG_PROGRAM(C) generates the same empty statement in 2.69. However, the
"checking how $CC reports undeclared, standard C functions" test is new in
2.70. It seems to have been added specifically for Clang's sake, in commit
82ef7805faffa151e724aa76c245ec590d174580
<https://git.savannah.gnu.org/cgit/autoconf.git/commit/?id=82ef7805faffa151e724aa76c245ec590d174580>.
I don't like the way the logic added in this commit works -- even if we can
find a fix for the specific problem you hit, it seems likely to be trouble in
the future, not only for itself but for other tests. I added a whole block of
text to NEWS about how "running configure tests with warnings promoted to
errors is not supported" and now I discover we're doing that exact thing
ourselves :-( Only for AC_CHECK_DECL(S), but still.
I'm not all that familiar with clang. Does anyone have a better idea for how
to handle this quirk it has?
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/support/?110400>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
