On Aug 7 07:52, NightStrike wrote: > On Tue, Aug 7, 2012 at 5:48 AM, Corinna Vinschen <[email protected]> wrote: > > Additionally I set AC_PREREQ to 2.68, rather than 2.69. 2.69 is not > > really required, and it disallows to autoconf on Fedora 17. > > We have only kept that as a requirement for the branches. Trunk > always stays as current as we can with autoconf / automake. It's very > easy to fall behind with those tools. Yes, it means that if your > distro doesn't stay current, then you need stock tools yourself. > However, building them is almost a no-op. There's no configuration > necessary (as in, args to configure), they have no non-trivial > dependencies, it's all just perl scripts. > > Initially, I tried to use Fedora as a sounding board for what version > to stay with, and it was just way too constraining, to the point where > I think Ozkan, or somebody else, was keeping versions of the autotools > in our FRS for easy download. I'd like to not go back to that. > > Again, this is for trunk, which is by definition cutting edge. > Branches are at whatever Ozkan wants them to be at.
I really don't see a reason to update autotools unless you really use a facility of the new version. The AC_PREREQ is only supposed to specify a minimal version required to build the configure file. It's not supposed to segregate older autoconf versions if they would be perfectly ok to build a configure file from a given configure.ac. Corinna ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
