libtool-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Unify line endings in localization test


From: Peter Rosin
Subject: Unify line endings in localization test
Date: Sat, 17 Jan 2009 00:42:34 +0100
User-agent: Thunderbird 2.0.0.19 (Windows/20081209)

Hi!

In the localization test, the output of the compiler is compared
with the grepped output of the compiler when run through libtool.

MSVC outputs its messages with \r\n, but the grep in the above
strips that down to just \n on MSYS. So, when the output is
diffed, there is a test failure.

Ok to push? Or should I just push it to the pr-msvc-support branch
for now?

Cheers,
Peter

2009-01-17  Peter Rosin  <address@hidden>

        Unify line endings in localization test.
        * tests/localization.at: Process both the expected output and
        the libtool output in the same manner in order to eliminate
        line ending differences. Fixes the test on MSYS/MSVC.

diff --git a/tests/localization.at b/tests/localization.at
index d489fef..e0a00b6 100644
--- a/tests/localization.at
+++ b/tests/localization.at
@@ -43,7 +43,7 @@ AT_CHECK([$CC $CPPFLAGS $CFLAGS -c b.c || exit 77], [], 
[stdout], [stderr])
 
 # Find out about expected output.
 AT_CHECK([$CC $CPPFLAGS $CFLAGS -c a.c || exit 1], [1], [stdout], [stderr])
-mv -f stdout expected-stdout
+grep -v thisisprobablynotmatching stdout > expected-stdout
 mv -f stderr expected-stderr
 AT_CHECK([$LIBTOOL --mode=compile --tag=CC $CC $CPPFLAGS $CFLAGS -c a.c || 
exit 1],
         [1], [stdout], [stderr])

reply via email to

[Prev in Thread] Current Thread [Next in Thread]