Re: tests/execute-mode.at

[Peter Rosin]

Den 2009-11-25 16:43 skrev Peter Rosin:
> tests/execute-mode.at uses AT_CHECK (line 172) to test if
> an executable is wrking. That fails when doing a cross
> build. Simply changing it to LT_AT_EXEC_CHECK doesn't work,
> probably because of the "weird" characters involved in
> the arguments.

Nope, that guess was wrong, it was because of arguments after
the executable and invoking with $LIBTOOL --mode=execute...

How about this patch? It fixes my cross build and passes on
native Linux.

LT_AT_NOINST_EXEC_CHECK seems to add $EXEEXT so I dropped it.

2009-11-25  Peter Rosin  <address@hidden>

        Fix cross build issue in execute mode test.
        * tests/execute-mode.at: Skip test for cross builds.

diff --git a/tests/execute-mode.at b/tests/execute-mode.at
index a1f2017..a1a1ee2 100644
--- a/tests/execute-mode.at
+++ b/tests/execute-mode.at
@@ -169,8 +169,8 @@ AT_CHECK([$LIBTOOL --mode=execute ./foo lt-wrapper "arg  
with special chars: \$!
         [], [./lt-real
 arg  with special chars: $!&*`'()
 ])
-AT_CHECK([$LIBTOOL --mode=execute ./main$EXEEXT "arg  with special chars: 
\$!&*\`'()"],
-        [], [stdout])
+LT_AT_NOINST_EXEC_CHECK([./main], [], [], [stdout], [ignore],
+                       ["arg  with special chars: \$!&*\`'()"])
 AT_CHECK([$FGREP 'arg  with special chars: $!&*`'\''()' stdout], [], [ignore])

 # We always pair two args.  The first one is never the empty string.

(I hope it didn't get wrapped...)

Cheers,
Peter

--
They are in the crowd with the answer before the question.
> Why do you dislike Jeopardy?