Re: use $EXEEXT consistently in new testsuite

[Roumen Petrov]

Ralf Wildenhues wrote:
> Hi Roumen,
>
> * Roumen Petrov wrote on Wed, Nov 26, 2008 at 12:46:00AM CET:
> > I will check this failure:
> > 28: Runpath in libtool library files                FAILED  
> > (runpath-in-lalib.at:59)

You recent commit fix this 10x.

> > The other not "ok" test:
> >  21: F77 convenience archives   skipped (convenience.at:110)
> >  22: FC convenience archives    skipped (convenience.at:170)
> >  23: Java convenience archives  skipped (convenience.at:267)
> > It is time to install those tools :( ;)
>
> Well, if you don't have them, don't worry.

Now my environment is with Fortran and Java tools.
Tests 21 and 22 - ok.
For test 23 - one more $EXEEXT. Please see attached file 
"libtool-origin-20081127.diff"


> >  29: static linking flags for programs skipped (static.at:177)
>
> Yes, I've seen this one as well with a linux->mingw cross.
[SNIP]

> >  74: Run tests with low max_cmd_len FAILED (cmdline_wrap.at:43)
> > Still no time to look into this one.
>
> This is a followup failure of 28 above.  
Yes. I realize it again.

[SNIP]

diff --git a/tests/convenience.at b/tests/convenience.at
index 995c8ff..c689811 100644
--- a/tests/convenience.at
+++ b/tests/convenience.at
@@ -263,7 +263,7 @@ EOF
   # libgcj.spec or unable to find it.  Skip this test for them.
   if test $i -eq 1; then
     AT_CHECK([$GCJ $GCJFLAGS -c foo1.java || exit 77], [], [ignore], [ignore])
-    AT_CHECK([$GCJ $GCJFLAGS --main=foo1 -o foo1 foo1.java A1.java || exit 
77],[],[ignore],[ignore])
+    AT_CHECK([$GCJ $GCJFLAGS --main=foo1 -o foo1$EXEEXT foo1.java A1.java || 
exit 77],[],[ignore],[ignore])
     AT_CHECK([./foo1$EXEEXT || exit 77],[],[ignore],[ignore])
     rm -f foo1.o foo1.obj foo1$EXEEXT
   fi