linuxmaniac created an issue (kamailio/kamailio#4337)
Forwarded from https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1085171
```
From: Niko Tyni <nt...@debian.org>
To: sub...@bugs.debian.org
Subject: kamailio: nondeterministic FTBFS on arm64: parallel build issue?
Date: Tue, 15 Oct 2024 20:33:13 +0300
Source: kamailio
Version: 5.8.3-1
Severity: important
This package failed to build from source with Perl 5.40 on arm64,
but succeeded on the second try.
https://buildd.debian.org/status/package.php?p=kamailio
It looks the build invokes bison multiple times on the same file,
presumably sometimes corrupting the result during parallel builds as
there's no locking. I doubt it's really architecture specific. Maybe
disable parallel building if there's no better fix?
>From
>https://buildd.debian.org/status/fetch.php?pkg=kamailio&arch=arm64&ver=5.8.3-1%2Bb1&stamp=1728980792&raw=0
bison -d -b core/cfg core/cfg.y
bison -d -b core/cfg core/cfg.y
Makefile.defs defs skipped
Makefile.defs defs skipped
gcc -fPIC -DPIC -pthread -DKSR_PTHREAD_MUTEX_SHARED -Wall -Wdate-time
-D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security
-mbranch-protection=standard -DVERSION_NODATE -DNAME='"kamailio"'
-DVERSION='"5.8.3"' -DARCH='"aarch64"' -DOS='linux_' -DOS_QUOTED='"linux"'
-DCOMPILER='"gcc 14.2.0"' -D__CPU_aarch64 -D__OS_linux -DVERSIONVAL=5008003
-DCFG_DIR='"/etc/kamailio/"' -DSHARE_DIR='"/usr/share/kamailio/"'
-DRUN_DIR='"/var/run/kamailio/"' -DPKG_MALLOC -DSHM_MMAP -DDNS_IP_HACK
-DUSE_MCAST -DUSE_TCP -DDISABLE_NAGLE -DHAVE_RESOLV_RES -DUSE_DNS_CACHE
-DUSE_DNS_FAILOVER -DUSE_DST_BLOCKLIST -DUSE_NAPTR -DMEM_JOIN_FREE -DF_MALLOC
-DQ_MALLOC -DTLSF_MALLOC -DDBG_SR_MEMORY -DUSE_TLS -DTLS_HOOKS -DUSE_CORE_STATS
-DSTATISTICS -DMALLOC_STATS -DUSE_SCTP -DNOSMP -DFAST_LOCK -DADAPTIVE_WAIT
-DADAPTIVE_WAIT_LOOPS=1024 -DHAVE_GETHOSTBYNAME2 -DHAVE_UNION_SEMUN
-DHAVE_SCHED_YIELD -DHAVE_MSG_NOSIGNAL -DHAVE_MSGHDR_MSG_CONTROL
-DHAVE_ALLOCA_H -DHAVE_TIMEGM -DHAVE_SCHED_SETSCHEDULER -DHAVE_IP_MREQN
-DUSE_RAW_SOCKS -DHAVE_EPOLL -DHAVE_SIGIO_RT -DSIGINFO64_WORKAROUND -DUSE_FUTEX
-DHAVE_SELECT -DMOD_NAME='"async"' -DMOD_NAMEID='async' -c async_mod.c -o
async_mod.o
flex -o core/lex.yy.c core/cfg.lex
gcc -pthread -DKSR_PTHREAD_MUTEX_SHARED -Wall -Wdate-time
-D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security
-mbranch-protection=standard -DVERSION_NODATE -DNAME='"kamailio"'
-DVERSION='"5.8.3"' -DARCH='"aarch64"' -DOS='linux_' -DOS_QUOTED='"linux"'
-DCOMPILER='"gcc 14.2.0"' -D__CPU_aarch64 -D__OS_linux -DVERSIONVAL=5008003
-DCFG_DIR='"/etc/kamailio/"' -DSHARE_DIR='"/usr/share/kamailio/"'
-DRUN_DIR='"/var/run/kamailio/"' -DPKG_MALLOC -DSHM_MMAP -DDNS_IP_HACK
-DUSE_MCAST -DUSE_TCP -DDISABLE_NAGLE -DHAVE_RESOLV_RES -DUSE_DNS_CACHE
-DUSE_DNS_FAILOVER -DUSE_DST_BLOCKLIST -DUSE_NAPTR -DMEM_JOIN_FREE -DF_MALLOC
-DQ_MALLOC -DTLSF_MALLOC -DDBG_SR_MEMORY -DUSE_TLS -DTLS_HOOKS -DUSE_CORE_STATS
-DSTATISTICS -DMALLOC_STATS -DUSE_SCTP -DNOSMP -DFAST_LOCK -DADAPTIVE_WAIT
-DADAPTIVE_WAIT_LOOPS=1024 -DHAVE_GETHOSTBYNAME2 -DHAVE_UNION_SEMUN
-DHAVE_SCHED_YIELD -DHAVE_MSG_NOSIGNAL -DHAVE_MSGHDR_MSG_CONTROL
-DHAVE_ALLOCA_H -DHAVE_TIMEGM -DHAVE_SCHED_SETSCHEDULER -DHAVE_IP_MREQN
-DUSE_RAW_SOCKS -DHAVE_EPOLL -DHAVE_SIGIO_RT -DSIGINFO64_WORKAROUND -DUSE_FUTEX
-DHAVE_SELECT -c core/lex.yy.c -o core/lex.yy.o
In file included from core/cfg.lex:40:
core/cfg.tab.h:49: error: unterminated #ifndef
49 | #ifndef YYTOKENTYPE
--
Niko Tyni nt...@debian.org
```
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/4337
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/4...@github.com>
_______________________________________________
Kamailio - Development Mailing List -- sr-dev@lists.kamailio.org
To unsubscribe send an email to sr-dev-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the
sender!