On Tue, Feb 05, 2008 at 08:51:42PM +0100, Ralf Wildenhues wrote: > * Patrick Welche wrote on Sat, Feb 02, 2008 at 06:09:03PM CET: > > - one strange thing: I tried running the testsuite -v -d 122 on its own > > in tests/testsuite.dir/122 after it passed with all the rest, and got > > What *exactly* did you do? This? > cd tests/testsuite.dir/122 > ./run > > If not, then how can I reproduce it? cd tests/testsuite.dir/122 ../../testsuite -v -d 122 Not the best way then... > > /torture.at:270: test -f "$file.in" || exit 77 > > There should be a path before the `/' here. > > > /torture.at:271: ./config.status "--file=$file:$file.in" > > --- /dev/null 2008-02-02 17:02:05.000000000 +0000 > > +++ /usr/src/local/autoconf.git/tests/testsuite.dir/122/testsuite.dir/at-stderr 2008-02-02 17:02:05.000000000 +0000 > > @@ -0,0 +1 @@ > > +config.status: error: cannot find input file: file.in > > stdout: > > /torture.at:271: exit code was 1, expected 0 and of course now after several checks, everything in autoconf passes (with your patch) and I can't reproduce the oddity. Cheers, Patrick _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
