> -----Original Message----- > From: Keith Marshall [mailto:keith.d.marshall@xxxxxxxxxxxx] > Sent: Tuesday, September 23, 2008 06:44 > To: autoconf@xxxxxxx > Cc: Howard Larson; 'Ralf Wildenhues'; 'Eric Blake' > Subject: Re: [autoconf 2.63] 95 of 353 tests fail > > On Friday 19 September 2008 21:31:15 Howard Larson wrote: > > > FWIW Ralf, I've just built autoconf-2.63 on an MSYS-1.0.11 box at > > > work. No errors in building. I've left the testsuite running, > > > but will not be able to report the final result until Monday; (I > > > don't use msw on my own boxes). > > > > > > So far, (it has reached test #230), eleven tests have been > > > skipped: (26, 27, 28, 167, 168, 169, 170, 171, 183, 184 and 218), > > > and there has been one expected failure: (91); all the rest have > > > reported `ok'. > > > > I did not receive errors for the autoconf build, either. Nor, for > > the automake build. It is when the libtool build failed that I > > began to investigate starting with autoconf make check. > > I don't dispute that you are experiencing problems, which I may not be > seeing; the above is merely an indication that, at the point where I > left it on Friday afternoon, I was seeing no evidence of any problem. > > Indeed, on returning to it, I find that I am unable to reproduce your > problem:-- > > ## ----------------------------- ## > ## GNU Autoconf 2.63 test suite. ## > ## ----------------------------- ## > > testsuite: command line was: > $ ./testsuite > > [...] > > testsuite: ending at: Fri Sep 19 20:43:12 GMTDT 2008 > testsuite: test suite duration: 7h 16m 27s > > ## ------------- ## > ## Test results. ## > ## ------------- ## > > 352 tests behaved as expected. > 12 tests were skipped. > > So, what are we doing differently, or what system differences do we > have, which allow me to complete this without errors, where you are > experiencing difficulties? > > FTR, my system is Win2K-SP4, with MSYS-1.0.10 installed, and upgraded > subsequently to MSYS-1.0.11, by simply installing the update packages > as they have been made available. I did:-- > > $ mkdir -p foo/bld-autoconf > $ cd foo > $ bunzip2 -c ~/download/autoconf-2.63.tar.bz2 | tar xf - > $ cd bld-autoconf > $ ../autoconf-2.63/configure > $ make > $ make check > > Full testsuite.log is attached. > > -- > > Regards, > Keith. > As an experiment, I tried to build m4 using the directory structure described by Keith. make failed on entering /c/GnuWin32/m4build/lib/stdlib.h with error 'cannot open include file: '' The same error previously ocurred for libtool make. I think this is significant. Why are the header files being written with #include ''? Regards, Howard Larson _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
