On 02/24/2011 11:45 AM, Tadeus (Eus) Prastowo wrote: > Hi! > > I cloned the development tree and checked out AUTOCONF-2.60. > Then, I did: > ./configure --prefix=/my/personal/dev/tree > make > make check > > All tests are okay except four testsuites related to Fortran: 147-150. > I googled and found a thread about the testsuites > (http://lists.gnu.org/archive/html/bug-autoconf/2008-03/msg00067.html) > but the problem is different from mine. > > Is there any suggestion as to how I can debug this problem? My OS is > GNU/Linux Ubuntu 9.04. Thanks for the report. Any reason why you are focusing on 2.60, rather than the latest? How does the testsuite fare for 2.68 or the latest git head? If the tests pass using newer code, then you can chalk these failures up to bugs in the older testsuite, and probably avoid any worries about them. And at that point, you could use a git bisect to determine exactly which patch fixed the failures, and cherry-pick just that patch back to your older checkout point. On the other hand, if the failures still persist with the latest sources, then you're more likely to get ideas for debugging since it is still a real problem worth fixing. -- Eric Blake eblake@xxxxxxxxxx +1-801-349-2682 Libvirt virtualization library http://libvirt.org
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
