From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Cc: Patrick Steinhardt <ps@pks.im>, Junio C Hamano <gitster@pobox.com>
Subject: clar unit testing framework FTBFS on uclibc systems (wchar_t unsupported)
Date: Thu, 17 Oct 2024 10:51:05 +0700 [thread overview]
Message-ID: <ZxCJqe4-rsRo1yHg@archie.me> (raw)
[-- Attachment #1: Type: text/plain, Size: 2838 bytes --]
Hi,
Since clar unit testing framework was imported by commit 9b7caa2809cb (t:
import the clar unit testing framework, 2024-09-04), Git FTBFS on uclibc
systems built by Buildroot:
```
CC t/unit-tests/unit-test.o
t/unit-tests/clar/clar.c: In function 'clar__assert_equal':
t/unit-tests/clar/clar.c:767:23: error: unknown type name 'wchar_t'
767 | const wchar_t *wcs1 = va_arg(args, const wchar_t *);
| ^~~~~~~
In file included from t/unit-tests/clar/clar.c:13:
t/unit-tests/clar/clar.c:767:58: error: unknown type name 'wchar_t'
767 | const wchar_t *wcs1 = va_arg(args, const wchar_t *);
| ^~~~~~~
t/unit-tests/clar/clar.c:768:23: error: unknown type name 'wchar_t'
768 | const wchar_t *wcs2 = va_arg(args, const wchar_t *);
| ^~~~~~~
t/unit-tests/clar/clar.c:768:58: error: unknown type name 'wchar_t'
768 | const wchar_t *wcs2 = va_arg(args, const wchar_t *);
| ^~~~~~~
t/unit-tests/clar/clar.c:769:65: warning: implicit declaration of function 'wcscmp' [-Wimplicit-function-declaration]
769 | is_equal = (!wcs1 || !wcs2) ? (wcs1 == wcs2) : !wcscmp(wcs1, wcs2);
| ^~~~~~
t/unit-tests/clar/clar.c:784:23: error: unknown type name 'wchar_t'
784 | const wchar_t *wcs1 = va_arg(args, const wchar_t *);
| ^~~~~~~
t/unit-tests/clar/clar.c:784:58: error: unknown type name 'wchar_t'
784 | const wchar_t *wcs1 = va_arg(args, const wchar_t *);
| ^~~~~~~
t/unit-tests/clar/clar.c:785:23: error: unknown type name 'wchar_t'
785 | const wchar_t *wcs2 = va_arg(args, const wchar_t *);
| ^~~~~~~
t/unit-tests/clar/clar.c:785:58: error: unknown type name 'wchar_t'
785 | const wchar_t *wcs2 = va_arg(args, const wchar_t *);
| ^~~~~~~
t/unit-tests/clar/clar.c:787:65: warning: implicit declaration of function 'wcsncmp' [-Wimplicit-function-declaration]
787 | is_equal = (!wcs1 || !wcs2) ? (wcs1 == wcs2) : !wcsncmp(wcs1, wcs2, len);
| ^~~~~~~
make[1]: *** [Makefile:2795: t/unit-tests/clar/clar.o] Error 1
```
See [1] for the full build log.
Thanks.
[1]: https://autobuild.buildroot.org/results/8cc9795dc18277926dd386eb1cb9f8c9b65b0042/build-end.log
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next reply other threads:[~2024-10-17 3:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 3:51 Bagas Sanjaya [this message]
2024-10-17 13:33 ` clar unit testing framework FTBFS on uclibc systems (wchar_t unsupported) Patrick Steinhardt
2024-10-17 13:54 ` Patrick Steinhardt
2024-10-17 20:08 ` Taylor Blau
2024-10-17 22:21 ` brian m. carlson
2024-10-18 4:51 ` Jeff King
2024-10-18 4:59 ` Patrick Steinhardt
2024-10-18 5:24 ` Jeff King
2024-10-18 5:31 ` Patrick Steinhardt
2024-10-18 20:50 ` Taylor Blau
2024-10-21 6:44 ` Patrick Steinhardt
2024-10-21 19:30 ` Jeff King
2024-10-21 19:41 ` Taylor Blau
2024-10-18 20:07 ` brian m. carlson
2024-10-21 19:19 ` Jeff King
2024-10-21 19:31 ` Jeff King
2024-10-18 13:49 ` Bagas Sanjaya
2024-10-21 6:44 ` Patrick Steinhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZxCJqe4-rsRo1yHg@archie.me \
--to=bagasdotme@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=ps@pks.im \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).