Re: use $EXEEXT consistently in new testsuite

2009-01-19 Thread Ralf Wildenhues
Hi Roumen, * Roumen Petrov wrote on Sun, Jan 04, 2009 at 02:56:54PM CET: > --- 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 |

Re: use $EXEEXT consistently in new testsuite

2009-01-04 Thread Roumen Petrov
Ping. Roumen Petrov wrote: [SNIP] 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" [SNIP] Roumen diff --git a/tests/convenience.at b/tests/convenience.at index 995c8ff..c689811 100644

Re: use $EXEEXT consistently in new testsuite

2008-11-27 Thread 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 filesFAILED (runpath-in-lalib.at:59) You recent commit fix this 10x. The other not "ok" test: 21: F77 convenience arch

Re: use $EXEEXT consistently in new testsuite

2008-11-27 Thread Ralf Wildenhues
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 filesFAILED > (runpath-in-lalib.at:59) Please post tests/testsuite.log, so we can see the verbose failure output. You can also run make check

Re: use $EXEEXT consistently in new testsuite

2008-11-25 Thread Roumen Petrov
Ralf Wildenhues wrote: * Ralf Wildenhues wrote on Sun, Nov 23, 2008 at 10:41:46PM CET: To fix the loose end wrt. the exec checks, there was some exit status normalization needed here. I think this patch should be sufficient, once the $EXEEXT patch is in (comes next). Here it is. I went over