https://bugs.kde.org/show_bug.cgi?id=404888
--- Comment #11 from Rhys Kidd <rhysk...@gmail.com> --- (In reply to Julian Seward from comment #9) > (In reply to Rhys Kidd from comment #7) > > I also wonder whether valgrind should be explicit about a minimum supported > > version of autoconf (via AC_PREREQ() macro)? > > I would be in favour of that. My only comment is that it should nevertheless > be a pretty old minimum version, because we'll want to support building V on > pretty old systems -- think ancient RHEL setups, etc. Is it realistic to > hope > for a minimum version that is, simultaneously, actually useful to enforce, > and > yet allows us to build on systems that are 5 years old? I was considering relying upon one of one of the following minimum versions, which provide a better trade off between quality-of-life features and support for older distributions: autoconf-2.60 released 2006-06-26 autoconf-2.63 released 2008-09-09 Even autoconf-2.68 is nearly a decade old having been released on 2010-09-22. I'd be surprised if RHEL 6+ didn't support at least autoconf-2.60. -- You are receiving this mail because: You are watching all bug changes.
