Hi Eric! On Thu, Feb 24, 2011 at 11:16 PM, Eric Blake <eblake@xxxxxxxxxx> wrote: > > This is why I try to build autoconf-2.60+ first to build the latest > version > > because my OS autoconf is just too old. > > Ah, I see. Yes, bootstrapping latest git requires an installed version > to be new enough. Still, it's easier to get to that state by starting > from a tarball (in fact, just install the 2.68 tarball rather than the > 2.60 tarball), rather than trying to recreate from the AUTOCONF2.60 > label in git. > Yup :-) But, I am wondering how the tarball can be released when not all test cases are okay ;-) That is the reason why I try to bootstrap from what I have in my git clone. Or, do the test cases fail for my setup but not for the setup by which the tarball was released? -- > Eric Blake eblake@xxxxxxxxxx +1-801-349-2682 > Libvirt virtualization library http://libvirt.org > > -- Best regards, Eus (FSF member #4445) In this digital era, where computing technology is pervasive, your freedom depends on the software controlling those computing devices. Join free software movement today! It is free as in freedom, not as in free beer! Join: http://www.fsf.org/ _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
