On mingw, in a testdir of vasnwprintf-posix, I see a test failure: ../../gltests/test-vasnwprintf-posix.c:4209: assertion 'wcscmp (result, L"00000000000303c 33") == 0' failed FAIL test-vasnwprintf-posix.exe (exit status: 3)
This patch fixes it. 2023-04-07 Bruno Haible <br...@clisp.org> vasnwprintf-posix tests: Avoid test failure on mingw. * tests/test-vasnwprintf-posix.c (test_function): For mingw, change two expected test results. diff --git a/tests/test-vasnwprintf-posix.c b/tests/test-vasnwprintf-posix.c index 125b9386a4..67e6654e5c 100644 --- a/tests/test-vasnwprintf-posix.c +++ b/tests/test-vasnwprintf-posix.c @@ -4205,7 +4205,7 @@ test_function (wchar_t * (*my_asnwprintf) (wchar_t *, size_t *, const wchar_t *, ASSERT (result != NULL); /* Neither ISO C nor POSIX specify that the '0' flag is ignored when a width and a precision are both present. But most implementations do so. */ - #if MUSL_LIBC || defined __MINGW32__ + #if MUSL_LIBC ASSERT (wcscmp (result, L"00000000000303c 33") == 0); #else ASSERT (wcscmp (result, L" 000000303c 33") == 0); @@ -4291,7 +4291,7 @@ test_function (wchar_t * (*my_asnwprintf) (wchar_t *, size_t *, const wchar_t *, ASSERT (result != NULL); /* Neither ISO C nor POSIX specify that the '0' flag is ignored when a width and a precision are both present. But most implementations do so. */ - #if MUSL_LIBC || defined __MINGW32__ + #if MUSL_LIBC ASSERT (wcscmp (result, L"0x000000000303c 33") == 0); #else ASSERT (wcscmp (result, L" 0x000000303c 33") == 0);