Victor recently fixed a problem I reported in #2288 and triggered a
builds for kamailio-[dev|5.3|5.2|5.1]-nightly
Is there a release schedule that shows me when I can expect the change
in kamailio-53 ?
apt considers the nightly release "5.3.3+0~20200417092406.72+bionic" as
a downgrade from "5.3.3+bionic".
--
Jeremy Kister
https://jeremy.kister.net./
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957395
>Package: src:kamailio
>Version: 5.3.2-1
>[..]
>The package fails to build in a test rebuild on at least amd64 with
>gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
>severity of this report will be raised before the bullseye release,
>so nothing has to be done for the buster release.
>
>The full build log can be found at:
>http://people.debian.org/~doko/logs/gcc10-20200225/kamailio_5.3.2-1_unstabl…
>The last lines of the build log are at the end of this report.
>
```
[...]
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:106:10: warning: ‘__builtin_strncpy’ specified bound depends on the length of the source argument [-Wstringop-overflow=]
106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest));
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
core/cfg.tab.c: In function ‘yyparse’:
core/cfg.y:669:48: note: length computed here
669 | strncpy($$, $1, strlen($1)+1);
| ^
In file included from /usr/include/string.h:495,
from core/cfg.y:40:
In function ‘strncpy’,
inlined from ‘yyparse’ at core/cfg.y:659:6:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:106:10: warning: ‘__builtin_strncpy’ specified bound depends on the length of the source argument [-Wstringop-overflow=]
106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest));
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
core/cfg.tab.c: In function ‘yyparse’:
core/cfg.y:659:35: note: length computed here
659 | strncpy($$, tmp, strlen(tmp)+1);
| ^~~
```
```
gcc -fPIC -DPIC -funroll-loops -Wcast-align -pthread -DKSR_PTHREAD_MUTEX_SHARED -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -DVERSION_NODATE -DNAME='"kamailio"' -DVERSION='"5.3.2"' -DARCH='"x86_64"' -DOS='linux_' -DOS_QUOTED='"linux"' -DCOMPILER='"gcc 0.0.1"' -D__CPU_x86_64 -D__OS_linux -DVERSIONVAL=5003002 -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_BLACKLIST -DUSE_NAPTR -DWITH_XAVP -DMEM_JOIN_FREE -DF_MALLOC -DQ_MALLOC -DTLSF_MALLOC -DDBG_SR_MEMORY -DUSE_TLS -DTLS_HOOKS -DUSE_CORE_STATS -DSTATISTICS -DMALLOC_STATS -DUSE_SCTP -DFAST_LOCK -DADAPTIVE_WAIT -DADAPTIVE_WAIT_LOOPS=1024 -DCC_GCC_LIKE_ASM -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_WORKARROUND -DUSE_FUTEX -DHAVE_SELECT -DMOD_NAME='"corex"' -c corex_rpc.c -o corex_rpc.o
gcc -shared -Wl,-O2 -Wl,-E -Wl,-z,relro -Wl,-z,now -pthread -rdynamic -ldl -Wl,-Bsymbolic-functions corex_var.o corex_nio.o corex_mod.o corex_lib.o corex_rpc.o -o corex.so
/usr/bin/ld: corex_mod.o:./src/modules/corex/corex_nio.h:36: multiple definition of `nio_min_msg_len'; corex_nio.o:./src/modules/corex/corex_nio.h:36: first defined here
/usr/bin/ld: corex_mod.o:./src/modules/corex/corex_nio.h:39: multiple definition of `nio_msg_avp_param'; corex_nio.o:./src/modules/corex/corex_nio.h:39: first defined here
/usr/bin/ld: corex_mod.o:./src/modules/corex/corex_nio.h:41: multiple definition of `nio_msg_avp_type'; corex_nio.o:./src/modules/corex/corex_nio.h:41: first defined here
/usr/bin/ld: corex_mod.o:./src/modules/corex/corex_nio.h:40: multiple definition of `nio_msg_avp_name'; corex_nio.o:./src/modules/corex/corex_nio.h:40: first defined here
/usr/bin/ld: corex_mod.o:./src/modules/corex/corex_nio.h:37: multiple definition of `nio_is_incoming'; corex_nio.o:./src/modules/corex/corex_nio.h:37: first defined here
/usr/bin/ld: corex_mod.o:./src/modules/corex/corex_nio.h:35: multiple definition of `nio_route_no'; corex_nio.o:./src/modules/corex/corex_nio.h:35: first defined here
collect2: error: ld returned 1 exit status
make[4]: *** [../../Makefile.rules:191: corex.so] Error 1
make[3]: *** [Makefile:513: modules] Error 1
make[3]: Leaving directory '/<<PKGBUILDDIR>>/src'
make[2]: *** [Makefile:34: all] Error 2
make[2]: Leaving directory '/<<PKGBUILDDIR>>'
make[1]: *** [debian/rules:146: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:130: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
```
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/2293
Module: kamailio
Branch: 5.3
Commit: 781a20ab23738d8a3639f3b973bb07df41b0735f
URL: https://github.com/kamailio/kamailio/commit/781a20ab23738d8a3639f3b973bb07d…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2020-04-22T15:01:26+02:00
modules: readme files regenerated - modules ... [skip ci]
---
Modified: src/modules/nathelper/README
---
Diff: https://github.com/kamailio/kamailio/commit/781a20ab23738d8a3639f3b973bb07d…
Patch: https://github.com/kamailio/kamailio/commit/781a20ab23738d8a3639f3b973bb07d…
---
diff --git a/src/modules/nathelper/README b/src/modules/nathelper/README
index 048372ae96..7cafc18603 100644
--- a/src/modules/nathelper/README
+++ b/src/modules/nathelper/README
@@ -273,11 +273,11 @@ modparam("nathelper", "natping_interval", 10)
4.3. ping_nated_only (integer)
- If this parameter is set to 1 then only contacts that have “behind_NAT”
- flag in user location database set will get ping.
+ If this parameter is set to 1 then only contacts that have the behind
+ NAT “nat_bflag” flag in user location database set will get ping.
- If it is 0 and sipping_flag is not set, then the 4-bytes UDP ping is
- sent to all contacts. If it is 0 and sipping_flag parameter is set,
+ If it is 0 and sipping_bflag is not set, then the 4-bytes UDP ping is
+ sent to all contacts. If it is 0 and sipping_bflag parameter is set,
then SIP-request-based pinging is sent to all contacts.
Default value is 0.