Hi Kevin, Yesterday kevin brintnall wrote:
> > * switched to using automake 1.11 which provides a 'silent' build process, > > causing errors and warnings to stand out much more than before. > > by Tobi Oetiker > > Tobi, > > Are all these version upgrades necessary? I think we should only insist > on the minimum version required to correctly build the software. > > -LIBTOOL_VER="1.5.6" > +LIBTOOL_VER="2.2.6" > > 1.5.6 continues to build rrdtool correctly on my system... > > -AUTOMAKE_VER="1.9.2" > +AUTOMAKE_VER="1.11" > > The new version is only 3 weeks old.. unlikely to be picked up by > packagers. I can still build correctly under 1.9.2. > > -AUTOCONF_VER="2.59" > +AUTOCONF_VER="2.63" > > I like 'AC_USE_SYSTEM_EXTENSIONS', available since 2.60. But, everything > still builds correctly on 2.60. Is it worth forcing this feature or can > we conditionally enable it? > > If there are other reasons that make the forced upgrade worthwhile, can > you elaborate? > > What do you think about the enclosed patch? > > - returns prerequisite versions to "minimum required" > - move AC_PREREQ() macro to the start of processing > - conditionally enables "silent" mode on autoconf 2.63 and greater. > - conditionally enables AC_USE_SYSTEM_EXTENSIONS no problem ... as long as I can use silent mode this is fine with me ... I wonder though, why would a packager need to run autogen unless he is packaging directly from the repository ? Releases as well as snapshots do not require any autoconf tools installed (or that is my intention at least). cheers tobi > -- Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland http://it.oetiker.ch [email protected] ++41 62 775 9902 / sb: -9900 _______________________________________________ rrd-developers mailing list [email protected] https://lists.oetiker.ch/cgi-bin/listinfo/rrd-developers
