• Bug#1065489: mongo-c-driver: FTBFS on armhf: format =?UTF-8?Q?=E2=80=98

    From Emanuele Rocca@21:1/5 to All on Tue Mar 5 12:50:01 2024
    Source: mongo-c-driver
    Version: 1.26.0-1.1
    Severity: serious
    Tags: ftbfs
    User: debian-arm@lists.debian.org
    Usertags: time-t

    Dear Maintainer,

    mongo-c-driver fails to build from source on armhf. The failure may be explained with the build flags introduced for the time64 migration,
    which are on by default on armhf:

    -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Werror=implicit-function-declaration

    [ 37%] Building C object src/libmongoc/CMakeFiles/mongoc_static.dir/src/mongoc/mongoc-error.c.o
    cd /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/src/libmongoc && /usr/bin/cc -DBSON_STATIC -DHAVE_STDARG_H -DHAVE_UNISTD_H -DKMS_MESSAGE_ENABLE_CRYPTO -DKMS_MESSAGE_ENABLE_CRYPTO_LIBCRYPTO -DKMS_MESSAGE_LITTLE_ENDIAN -DKMS_MSG_STATIC -DMCOMMON_NAME_PREFIX=_
    mongoc_mcommon -DMONGOC_COMPILATION -DMONGOC_STATIC -D_BSD_SOURCE -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=700 -I/<<PKGBUILDDIR>>/src/libmongoc/../kms-message/src -I/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/src/libmongoc/src -I/<<PKGBUILDDIR>>/obj-arm-linux-
    gnueabihf/src/libmongoc/src/mongoc -I/<<PKGBUILDDIR>>/src/libmongoc/src -I/<<PKGBUILDDIR>>/src/libmongoc/src/mongoc -I/<<PKGBUILDDIR>>/src/libmongoc/../../src/common -I/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/src/libmongoc/../../src -I/<<PKGBUILDDIR>>/
    obj-arm-linux-gnueabihf/src/libmongoc/../../src/common -I/<<PKGBUILDDIR>>/src/libbson/src -I/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/src/libbson/src -I/<<PKGBUILDDIR>>/src/common -I/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/src/common -g -O2 -Werror=
    implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -std=c99 -
    Werror=implicit -Werror=return-type -Werror=incompatible-pointer-types -Werror=int-conversion -Werror=discarded-qualifiers -Werror=uninitialized -Werror -pedantic -Wall -Wempty-body -Wexpansion-to-defined -Wformat -Wformat-nonliteral -Wformat-security -
    Winit-self -Wmissing-include-dirs -Wredundant-decls -Wshadow -Wstrict-prototypes -Wswitch-default -Wswitch-enum -Wundef -Wuninitialized -Wno-strict-aliasing -fPIC -DUTF8PROC_EXPORTS -MD -MT src/libmongoc/CMakeFiles/mongoc_static.dir/src/mongoc/mongoc-
    error.c.o -MF CMakeFiles/mongoc_static.dir/src/mongoc/mongoc-error.c.o.d -o CMakeFiles/mongoc_static.dir/src/mongoc/mongoc-error.c.o -c /<<PKGBUILDDIR>>/src/libmongoc/src/mongoc/mongoc-error.c
    /<<PKGBUILDDIR>>/src/libmongoc/src/mongoc/mongoc-log.c: In function ‘mongoc_log_default_handler’:
    /<<PKGBUILDDIR>>/src/libmongoc/src/mongoc/mongoc-log.c:215:21: error: format ‘%ld’ expects argument of type ‘long int’, but argument 4 has type ‘__suseconds64_t’ {aka ‘long long int’} [-Werror=format=]
    215 | "%s.%04ld: [%5d]: %8s: %12s: %s\n",
    | ~~~~^
    | |
    | long int
    | %04lld
    216 | nowstr,
    217 | tv.tv_usec / 1000L,
    | ~~~~~~~~~~~~~~~~~~
    | |
    | __suseconds64_t {aka long long int}
    cc1: all warnings being treated as errors
    make[3]: *** [src/libmongoc/CMakeFiles/mongoc_shared.dir/build.make:765: src/libmongoc/CMakeFiles/mongoc_shared.dir/src/mongoc/mongoc-log.c.o] Error 1

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Debian Bug Tracking System@21:1/5 to All on Fri Mar 8 21:00:02 2024
    This is a multi-part message in MIME format...

    Your message dated Fri, 08 Mar 2024 19:50:47 +0000
    with message-id <E1rigEx-0027Bn-QP@fasolo.debian.org>
    and subject line Bug#1065489: fixed in mongo-c-driver 1.26.1-1
    has caused the Debian Bug report #1065489,
    regarding mongo-c-driver: FTBFS on armhf: format ‘%ld’ expects argument of type ‘long int’, but argument 4 has type ‘__suseconds64_t’ {aka ‘long long int’}
    to be marked as done.

    This means that you claim that the problem has been dealt with.
    If this is not the case it is now your responsibility to reopen the
    Bug report if necessary, and/or fix the problem forthwith.

    (NB: If you are a system administrator and have no idea what this
    message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org
    immediately.)


    --
    1065489: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065489
    Debian Bug Tracking System
    Contact owner@bugs.debian.org with problems

    Received: (at submit) by bugs.debian.org; 5 Mar 2024 11:44:06 +0000 X-Spam-Checker-Version: SpamAssassin 3.4.6-bugs.debian.org_2005_01_02
    (2021-04-09) on buxtehude.debian.org
    X-Spam-Level:
    X-Spam-Status: No, score=-5.9 required=4.0 tests=BAYES_00,DKIM_SIGNED,
    DKIM_VALID,DKIM_VALID_EF,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM,
    FROMDEVELOPER,HEADER_FROM_DIFFERENT_DOMAINS,RCVD_IN_DNSWL_NONE,
    SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham
    autolearn_force=no version=3.4.6-bugs.debian.org_2005_01_02 X-Spam-Bayes: score:0.0000 Tokens: new, 41; hammy, 150; neutral, 131; spammy,
    0. spammytokens: hammytokens:0.000-+--pkgbuilddir,
    0.000-+--PKGBUILDDIR, 0.000-+--armhf, 0.000-+--fPIC, 0.000-+--Wdatetime Return-path: <emarocca@gmail.com>
    Received: from mail-ej1-x636.google.com ([2a00:1450:4864:20::636]:39165)
    by buxtehude.debian.org with esmtps (