12 May
2016
12 May
'16
11:38 a.m.
Le Thu, 12 May 2016 12:03:59 +0300,
Juha Heinanen <jh(a)tutpro.com> a écrit :
Perhaps it has to do with some other defines. Do you
remember what
to add to debian/rules in order to see all gcc parameters during
compilation?
I add "Q=0" on the make command line to see the full compiler's command
line. For the specific case of the tlsf_malloc.c compilation, with
MEMDBG previously configured to 1, it shows:
gcc
-g
-funroll-loops
-Wcast-align
-m64
-minline-all-stringops
-falign-loops
-ftree-vectorize
-fno-strict-overflow
-Wall
-DNAME='"kamailio"'
-DVERSION='"5.0.0-dev4"'
-DARCH='"x86_64"'
-DOS='linux_'
-DOS_QUOTED='"linux"'
-DCOMPILER='"gcc 4.9.2"'
-D__CPU_x86_64
-D__OS_linux
-DSER_VER=5000000
-DCFG_DIR='"/usr/local/etc/kamailio/"'
-DRUN_DIR='"/var/run/kamailio/"'
-DPKG_MALLOC
-DSHM_MEM
-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
-DWITH_AS_SUPPORT
-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
-DUSE_RAW_SOCKS
-DHAVE_EPOLL
-DHAVE_SIGIO_RT
-DSIGINFO64_WORKARROUND
-DUSE_FUTEX
-DHAVE_SELECT
-c mem/tlsf_malloc.c
-o mem/tlsf_malloc.o
-MMD
-MP
and no warning on my machine.
--
Camille