Hello,

can you say what is the command you use the compile kamailio/kex module?
The flags from the version output are not complete, just a selection of
them.

f_malloc is the default in 4.3.

Cheers,
Daniel

On 28/08/15 10:54, Carsten Bock wrote:
> Hi,
>
> quick question:
>
> We've compiled Kamailio with the following settings:
>
> version: kamailio 4.3.1 (x86_64/linux) 7cd85b
> flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS,
> USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM,
> SHM_MMAP, F_MALLOC, DBG_F_MALLOC, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT,
> USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST,
> HAVE_RESOLV_RES
> ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16,
> MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB
> poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
> id: 7cd85b
>
> (we are using F_MALLOC to do some memory debugging)
>
> However, with this compiler settings, we cannot use the "kex" module anymore:
>
> kamailio -c
> loading modules under config path:
> /usr/lib64/kamailio/modules/:/usr/lib/kamailio/modules/:/usr/lib/x86_64-linux-gnu/kamailio/modules/
>  0(25506) ERROR: <core> [sr_module.c:574]: load_module(): could not
> open module </usr/lib/x86_64-linux-gnu/kamailio/modules/kex.so>:
> /usr/lib/x86_64-linux-gnu/kamailio/modules/kex.so: undefined symbol:
> pkg_info
>  0(25506) : <core> [cfg.y:3432]: yyerror_at(): parse error in config
> file /etc/kamailio/kamailio.cfg, line 63, column 12-16: failed to load
> module
>
> Looking at the files at "mem/*", the pkg_info seems to be defined for me.
> Does anyone (with more knowledge on the Memory stuff) have a clue, why
> this is not working?
>
> Thanks,
> Carsten
>
>
>

-- 
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.com


_______________________________________________
sr-dev mailing list
sr-dev@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev

Reply via email to