[PATCH] tests: use dry runs in both parts of 'check link mode operation'

Hi!

I'm pushing this as obvious as this was how link-2.test used to
do it.

Cheers,
Peter


From 82791b3fb7043f81391bb36047f8533f4dd11b7b Mon Sep 17 00:00:00 2001
From: Peter Rosin <[email protected]>
Date: Sun, 7 Oct 2012 00:57:10 +0200
Subject: [PATCH] tests: use dry runs in both parts of 'check link mode operation'

MSVC exits with status 2 instead of the expected 1 when a
real link is attempted.

* tests/libtool.at (check link mode operation): Use a dry run and
expect a clean exit status instead of expecting a fail.

Signed-off-by: Peter Rosin <[email protected]>
---
 tests/libtool.at |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/tests/libtool.at b/tests/libtool.at
index 4ab405c..3bcdfe5 100755
--- a/tests/libtool.at
+++ b/tests/libtool.at
@@ -192,7 +192,7 @@ pic_object=none
 non_pic_object=hell.o
 ]])

-AT_CHECK([$LIBTOOL --mode=link $CC -o something foo.o hell.lo], [1], [stdout], [ignore])
+AT_CHECK([$LIBTOOL -n --mode=link $CC -o something foo.o hell.lo], [0], [stdout], [ignore])
 AT_CHECK([$FGREP '.lo ' stdout], [1], [ignore])

 AT_CLEANUP
--
1.7.9