> This is a subtle change in semantics; beforehand, the if-failed code ($3) was > executed while the compiler output still existed, and could theoretically > rerun > conftest$ac_exeext with an argument; now the files are removed before the if- > failed code is run. Was this intentional? IMHO, it is a harmless change (I > doubt anyone wrote an if-failed condition which was that closely tied to our > undocumented internals, and even if they did, they are obviously so familiar > with our internals that they should be able to compensate); and so far, in my > testing with this applied, I haven't seen any packages hiccup.
There are many, actually: http://www.google.com/codesearch?hl=en&lr=&q=file%3Aconfigure.(ac|in)+\[(.*grep.*|.*sed.*|.*awk.*|.*\.\%2F)conftest&sbtn=Search Paolo
