|
From: | Roumen Petrov |
Subject: | Re: use $EXEEXT consistently in new testsuite |
Date: | Wed, 26 Nov 2008 01:46:00 +0200 |
User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.18) Gecko/20081114 SeaMonkey/1.1.13 |
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 tests/*.at and hopefully found all instances needing $EXEEXT now. Pushed. Review appreciated. Cheers, Ralf
[SNIP] I will check this failure:28: Runpath in libtool library files FAILED (runpath-in-lalib.at:59)
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 :( ;) 29: static linking flags for programs skipped (static.at:177)35: static library contains static library expected failure (archive-in-archive.at:49)
68: build tree relpaths expected failure (deplibs-ident.at:68) 74: Run tests with low max_cmd_len FAILED (cmdline_wrap.at:43) Still no time to look into this one. 75: darwin fat compile skipped (darwin.at:42) fine (test is on linux) Roumen
[Prev in Thread] | Current Thread | [Next in Thread] |