> I'm not sure what that means, whether a wrong version of > autoconf/automake was used (though when I accidentally tried that, it > has always complained loudly) or if some environment difference can > cause this. Perhaps I should change the script not to care about > commits though that won't happen soon (or perhaps I should drop the > checks completely) but would people be OK with me checking in the patch > above (with appropriate ChangeLog) to silence buildbot for a while > again?
Hmm, I made sure to regenerate them on an Intel compile-farm machine because my local autoconf/automake was too new. I thought that I also regenerated after the last rebase before pushing. But maybe it auto-merged that change at some point and I forgot? Regards Robin
