> > was somehow a little more informative, in terms of reporting the line in > > the original configure.in where the invalid variable value was possibly > > set. So I wouldn't have to harass you folks. > > Yes, that would be nice. Difficult to achieve though, unfortunately. > The piece of code that does the substitutions is in a hot path, i.e., > any slowdowns there will be quite noticable to users. You could get > into the habit of echoing the variables that you set, with combinations > of AC_MSG_CHECKING and AC_MSG_RESULT for example. Perhaps some flag could be available that if enabled in configure.in it enables that extra checking in the hot path. I've been echoing the variables I set, and still missed it. Oh well. Just something to think about. Thanks again. _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
