|
From: | Ralf Corsepius |
Subject: | Re: autoconf-2.68: no AC_LANG_SOURCE call detected in body |
Date: | Thu, 23 Sep 2010 16:33:01 +0200 |
User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.9) Gecko/20100907 Fedora/3.1.3-1.fc13 Thunderbird/3.1.3 |
On 09/23/2010 03:52 PM, Eric Blake wrote:
Your feature is my regression - It broke what appeared to have worked for ages ;)On 09/23/2010 06:56 AM, Ralf Corsepius wrote:Hi, I am facing a new issue/regression with autoconf-2.68:That is not a regression, but a feature.
Reread NEWS:AC_COMPILE_IFELSE([ #ifndef FOO choke me #endif ])You should have used: AC_COMPILE_IFELSE([AC_LANG_SOURCE([ #ifndef FOO choke me #endif ])
OK, thanks.
Actually, I don't need the AC_DEFINES in this particular case - Adding them however, should not do much harm, either.With older autoconfs, autoreconf remains entirely silent.Not only were they entirely silent, but most likely generated a broken configure. If you don't use AC_LANG_SOURCE, then you don't get the benefit of all the prior AC_DEFINEs being implicitly included before the body of your test, which leads to documented cases of mis-diagnosing whether a feature is present for a given build.
Well, "really usable warnings" look a bit different than this warning. They might be self-explanatory to you, but to me this warning was "Greek".What is wrong with this configure.ac rsp. how to overcome these warnings?Use AC_LANG_SOURCE, like the warning told you to do in the first place.
Ralf
[Prev in Thread] | Current Thread | [Next in Thread] |