Source: erlang
Version: 1:25.3.2.10+dfsg-1
Severity: serious
Tags: ftbfs


https://buildd.debian.org/status/fetch.php?pkg=erlang&arch=armhf&ver=1%3A25.3.2.10%2Bdfsg-1&stamp=1711383511&raw=0

arm-linux-gnueabihf-gcc -Werror=undef -Werror=implicit -Werror=return-type -fno-strict-aliasing -fno-common -g -O2 -fno-strict-aliasing -I/<<PKGBUILDDIR>>/erts/arm-unknown-linux-gnueabihf -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -DHAVE_CONFIG_H -Wall -Wstrict- prototypes -Wpointer-arith -Wmissing-prototypes -Wdeclaration-after-statement -DUSE_THREADS -D_THREAD_SAFE -D_REENTRANT -DPOSIX_THREADS -D_POSIX_THREAD_SAFE_FUNCTIONS -Iarm-unknown-linux-gnueabihf/opt/emu -Ibeam -Isys/unix -Isys/common -Iarm-unknown-linux-gnueabihf -Ipcre -Iryu -Iopenssl/include -I../include -I../include/arm-unknown-linux-gnueabihf -I../include/internal -I../include/internal/arm-unknown-linux-gnueabihf -c sys/unix/sys_time.c -o obj/arm-unknown-linux-gnueabihf/opt/emu/sys_time.o
In file included from /usr/include/features.h:393,
from /usr/include/arm-linux-gnueabihf/bits/libc-header- start.h:33,
from /usr/include/stdlib.h:26,
from sys/unix/sys_time.c:35: /usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64"
26 | # error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64"
| ^~~~~


-- System Information:
Debian Release: trixie/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

This is a multi-part message in MIME format...

Your message dated Wed, 27 Mar 2024 08:37:43 +0000
with message-id <E1rpOn1-005BKx-Fd@fasolo.debian.org>
and subject line Bug#1067701: fixed in erlang 1:25.3.2.10+dfsg-2
has caused the Debian Bug report #1067701,
regarding FTBFS: _TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64
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.)


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

Received: (at submit) by bugs.debian.org; 25 Mar 2024 18:48:00 +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=-8.9 required=4.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID,FORGED_SPF_HELO,FOURLA,FROMDEVELOPER,SPF_HELO_PASS,SPF_NONE,
XMAILER_REPORTBUG autolearn=ham autolearn_force=no
version=3.4.6-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 40; hammy, 150; neutral, 130; spammy,
0. spammytokens: hammytokens:0.000-+--pkgbuilddir,
0.000-+--PKGBUILDDIR, 0.000-+--armhf, 0.000-+--sk:buildd.,
0.000-+--UD:buildd.debian.org
Return-path: <wrar@debian.org>
Received: from wrar.name ([116.203.248.210]:40358 helo=durkon.wrar.name)
by buxtehude.debian.org with esmtps (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256)
(Exim

This is a multi-part message in MIME format...

Your message dated Wed, 17 Apr 2024 18:50:52 +0000
with message-id <E1rxAMu-00FTrA-DJ@fasolo.debian.org>
and subject line Bug#1067701: fixed in erlang 1:26.2.4+dfsg-1
has caused the Debian Bug report #1067701,
regarding FTBFS: _TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64
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.)


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

Received: (at submit) by bugs.debian.org; 25 Mar 2024 18:48:00 +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=-8.9 required=4.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID,FORGED_SPF_HELO,FOURLA,FROMDEVELOPER,SPF_HELO_PASS,SPF_NONE,
XMAILER_REPORTBUG autolearn=ham autolearn_force=no
version=3.4.6-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 40; hammy, 150; neutral, 130; spammy,
0. spammytokens: hammytokens:0.000-+--pkgbuilddir,
0.000-+--PKGBUILDDIR, 0.000-+--armhf, 0.000-+--sk:buildd.,
0.000-+--UD:buildd.debian.org
Return-path: <wrar@debian.org>
Received: from wrar.name ([116.203.248.210]:40358 helo=durkon.wrar.name)
by buxtehude.debian.org with esmtps (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256)
(Exim