Compiling sip-router from clean checkout generates a lot of different warnings. What's the policy about this in the project? SHould we just forget or should we react?

In Asterisk we have a configuration flag for ./configure that is called "dev-mode" which forces warnings to generate an error and stop make. This helps motivating developers to fix warnings :-)

/O

gcc -g -O9 -funroll-loops -Wcast-align -m64 -minline-all-stringops - falign-loops -ftree-vectorize -fno-strict-overflow -mtune=opteron - Wall -DNAME='"ser"' -DVERSION='"2.99.99-pre3"' -DARCH='"x86_64"' - DOS='darwin_' -DOS_QUOTED='"darwin"' -DCOMPILER='"gcc 4.2.1"' - D__CPU_x86_64 -D__OS_darwin -DSER_VER=2099099 -DCFG_DIR='"/usr/local/ etc/ser/"' -DPKG_MALLOC -DSHM_MEM -DSHM_MMAP -DDNS_IP_HACK -DUSE_IPV6 - DUSE_MCAST -DUSE_TCP -DDISABLE_NAGLE -DHAVE_RESOLV_RES -DUSE_DNS_CACHE -DUSE_DNS_FAILOVER -DUSE_DST_BLACKLIST -DUSE_NAPTR -DDBG_QM_MALLOC - DUSE_TLS -DTLS_HOOKS -DFAST_LOCK -DADAPTIVE_WAIT - DADAPTIVE_WAIT_LOOPS=1024 -DCC_GCC_LIKE_ASM -DHAVE_SOCKADDR_SA_LEN - DHAVE_GETHOSTBYNAME2 -DHAVE_UNION_SEMUN -DHAVE_SCHED_YIELD - DHAVE_MSGHDR_MSG_CONTROL -DUSE_ANON_MMAP -DNDEBUG - DHAVE_CONNECT_ECONNRESET_BUG -DHAVE_TIMEGM -DUSE_SIGWAIT -DHAVE_KQUEUE -DHAVE_SELECT -c parser/sdp/sdp.c -o parser/sdp/sdp.o parser/sdp/sdp.c: In function 'parse_sdp': parser/sdp/sdp.c:707: warning: dereferencing type-punned pointer will break strict-aliasing rules parser/sdp/sdp.c:729: warning: dereferencing type-punned pointer will break strict-aliasing rules g