Hi Paul,
On mingw 10 and also with MSVC 14.30, the test-posixtm test fails:
FAIL: test-posixtm
==
0101.00 return value mismatch: got 0, expected 1
12312359.59 return value mismatch: got 0, expected 1
00010101.00 return value mismatch: got 0, expected 1
19011213204
Hi Paul,
As the nstrftime test is failing on several platforms [1], I'm trying to
debug it.
Now I'm on mingw 10. The output of test-nstrftime is sometimes
PST8PDT,M3.2.0,M11.1.0: expected "1969-12-31 16:00:00 -0800 (PST)", got
"1969-12-31 16:00:00 (PST)"
MST7: expected "1969-12-31 17:00:00 -07
On native Windows, I see a test failure:
FAIL: test-getumask
===
../../gltests/test-getumask.c:42: assertion 'mask == 002' failed
FAIL test-getumask.exe (exit status: 3)
There are two problems here:
- The getumask() implementation uses a temporary directory that may not
exist,
Paul Eggert wrote:
> > +LC_ALL=C ${CHECKER} test-dfa-match-aux '[[:foo:]]' a > tmp 2>&1
> > +LC_ALL=C tr -d '\r' < tmp > out
>
> This sort of change means we won't catch stray CRs in the output.
>
> Is there some way we can instead compile or run MinGW apps so that they
> instead follow the POSI
On 4/20/23 09:39, Bruno Haible wrote:
+LC_ALL=C ${CHECKER} test-dfa-match-aux '[[:foo:]]' a > tmp 2>&1
+LC_ALL=C tr -d '\r' < tmp > out
This sort of change means we won't catch stray CRs in the output.
Is there some way we can instead compile or run MinGW apps so that they
instead follow the
Building a testdir for module 'posixtm' on mingw and MSVC, I see this
link error:
../../gltests/test-posixtm.c: In function ‘main’:
../../gltests/test-posixtm.c:162:11: warning: implicit declaration of function
‘stpcpy’ [-Wimplicit-function-declaration]
162 | stpcpy (stpcpy (tmp_buf,
On mingw 10, I see this test failure:
FAIL: test-readtokens.sh
--- exp 2023-04-20 06:20:32.200323300 +0200
+++ out 2023-04-20 06:20:32.232259800 +0200
@@ -1 +1 @@
-a:b:c:
+a:b:c:
--- exp 2023-04-20 06:20:32.278874900 +0200
+++ out 2023-04-20 06:20:32.310364100 +0200
@@ -1
On mingw 10, I see this test failure:
FAIL: test-parse-duration.sh
../../gltests/test-parse-duration.sh: line 64: test: 38898367
: integer expression expected
test-parse-duration fatal error: 38898367
is not 38898367
FAIL test-parse-duration.sh (exit status: 1)
The
On mingw 10, I see this test failure:
FAIL: test-dfa-invalid-char-class.sh
--- exp 2023-04-20 06:15:56.778614400 +0200
+++ out 2023-04-20 06:15:56.857719400 +0200
@@ -1 +1 @@
-dfaerror: invalid character class
+dfaerror: invalid character class
FAIL test-dfa-i
On mingw 10.0.0, in a testdir configured without --enable-threads=windows,
most threads related tests fail:
FAIL: test-asyncsafe-spin2
FAIL: test-cond
FAIL: test-execute.sh
FAIL: test-execute-script
FAIL: test-fstrcmp
FAIL: test-immutable.sh
FAIL: test-localename
FAIL: test-rwlock1
FAIL: test-lock
A testdir of module 'mtx' fails to build on mingw and other platforms:
/usr/x86_64-w64-mingw32/bin/ld: test-mtx.o: in function `once_contender_thread':
../../gltests/test-mtx.c:365: undefined reference to `call_once'
collect2: error: ld returned 1 exit status
make[4]: *** [Makefile:4173: test-mtx.
A testdir for module 'execute' fails to compile on mingw:
../../gltests/test-execute-main.c: In function ‘main’:
../../gltests/test-execute-main.c:70:11: error: ‘SIGPIPE’ undeclared (first use
in this function); did you mean ‘SIGFPE’?
70 | signal (SIGPIPE, SIG_DFL);
| ^~~
With MSVC 14.30 (market name "Visual Studio 2022" [1]), I see compilation
errors in C++ mode:
/home/bruno/msvc/compile cl -nologo -DHAVE_CONFIG_H -DEXEEXT=\".exe\"
-DEXEEXT=\".exe\" -I. -I../../gltests -I.. -DGNULIB_STRICT_CHECKING=1
-DIN_GNULIB_TESTS=1 -I. -I../../gltests -I.. -I../../gltests/
13 matches
Mail list logo
