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

Bug#980597: liblangtag: FTBFS: check-extlang.c:45:26: error: too many arguments for format [-Werror=format-extra-args]



Source: liblangtag
Version: 0.6.3-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210120 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> gcc -DHAVE_CONFIG_H -I. -I..  -I../liblangtag -I.. -DTEST_DATADIR=\"/<<PKGBUILDDIR>>/data/\" -DTEST_MODDIR="\"/<<PKGBUILDDIR>>/extensions/.libs\"" -D__LANGTAG_COMPILATION -D__LANGTAG_PRIVATE -pthread  -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security  -Wall -Wstrict-prototypes -Wnested-externs -Werror=missing-prototypes -Werror=implicit-function-declaration -Werror=pointer-arith -Werror=init-self -Werror=format-security -Werror=format=2 -Werror=missing-include-dirs -Werror=return-type  -c -o check-extlang.o check-extlang.c
> In file included from main.h:17,
>                  from check-extlang.c:18:
> check-extlang.c: In function ‘test_lt_extlang_compare_fn’:
> check-extlang.c:45:26: error: too many arguments for format [-Werror=format-extra-args]
>    45 |  fail_unless(e1 != NULL, "No expected extlang found: 'yue'");
>       |                          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> check-extlang.c:46:42: error: too many arguments for format [-Werror=format-extra-args]
>    46 |  fail_unless(lt_extlang_compare(e1, e1), "extlang that points to the same object should be dealt as same");
>       |                                          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> check-extlang.c:48:26: error: too many arguments for format [-Werror=format-extra-args]
>    48 |  fail_unless(e2 != NULL, "No expected extlang found: 'hks'");
>       |                          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> check-extlang.c:49:43: error: too many arguments for format [-Werror=format-extra-args]
>    49 |  fail_unless(!lt_extlang_compare(e1, e2), "extlang that has different tag should be dealt as different.");
>       |                                           ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> check-extlang.c:52:26: error: too many arguments for format [-Werror=format-extra-args]
>    52 |  fail_unless(e2 != NULL, "No expected extlang found: '*'");
>       |                          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> check-extlang.c:53:42: error: too many arguments for format [-Werror=format-extra-args]
>    53 |  fail_unless(lt_extlang_compare(e1, e2), "wildcard should be matched with any objects.");
>       |                                          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> check-extlang.c:56:26: error: too many arguments for format [-Werror=format-extra-args]
>    56 |  fail_unless(e2 != NULL, "No expected extlang found: ''");
>       |                          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> check-extlang.c:57:43: error: too many arguments for format [-Werror=format-extra-args]
>    57 |  fail_unless(!lt_extlang_compare(e1, e2), "extlang that has different tag should be dealt as different even if it's an empty entry.");
>       |                                           ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> cc1: some warnings being treated as errors
> make[5]: *** [Makefile:1006: check-extlang.o] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2021/01/20/liblangtag_0.6.3-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with me
so that we can identify if something relevant changed in the meantime.

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.


Reply to: