On Wednesday 04 December 2024 00:23:44 Martin Storsjö wrote:
> On Tue, 3 Dec 2024, Pali Rohár wrote:
> 
> > Another option without touching binfmt-misc is misuse of automake
> > LOG_COMPILER env variable. It is prepended before spawning any test,
> > I guess it is for logging purpose. But it can be also wine which then
> > spawns exe binary. So for example:
> > 
> >  make check LOG_COMPILER=wine
> > 
> 
> Thanks!
> 
> The tests don't quite build with Clang right now:
> 
> In file included from ../testcases/t_snprintf1.c:2:
> ../testcases/t_snprintf_tmpl.h:7:13: error: call to undeclared library
> function 'snprintf' with type 'int (char *restrict, unsigned long long,
> const char *restrict, ...)'; ISO C99 and later do not support implicit
> function declarations [-Wimplicit-function-declaration]
>     7 |   int ret = snprintf(buffer, 3, "%s", "AAA");
>       |             ^
> 
> (This seems to be due to _CRTBLD in combination with
> -D__USE_MINGW_ANSI_STDIO=1.)
> 
> ../testcases/t_trycatch.cpp:3:18: error: ISO C++17 does not allow dynamic
> except
> ion specifications [-Wdynamic-exception-spec]
>     3 | void foo (int d) throw (int)
>       |                  ^~~~~~~~~~~
> ../testcases/t_trycatch.cpp:3:18: note: use 'noexcept(false)' instead
>     3 | void foo (int d) throw (int)
>       |                  ^~~~~~~~~~~
>       |                  noexcept(false)
> 1 error generated.
> 
> 
> ../testcases/t_tls1.c:22:2: error: No keyword for TLS vars is defined.
>    22 | #error No keyword for TLS vars is defined.
>       |  ^
> ../testcases/t_tls1.c:25:1: error: unknown type name '__threadlocal__'
>    25 | __threadlocal__ int tvar = 0;
>       | ^
> 2 errors generated.
> 
> 
> 
> If building with a toolchain that defaults to UCRT, I also get a bunch of
> more errors in these tests, due to undefined symbols like wprintf and
> __ms_vsscanf.
> 
> // Martin

Seems that the tests were not been running for a long time as nobody
complained yet. Normally distributions are running "make check" after
building & installing but seems that this is not a case for mingw-w64.

So it would be a good idea to revisit test suite...


_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Reply via email to