make[1]: Entering directory `/home/darilion/software/siprouter/sip-router/modules_s/pa' gcc -fPIC -DPIC -g -O9 -funroll-loops -Wcast-align -minline-all-stringops -falign-loops -ftree-vectorize -mtune=athlon64 -Wall -I/usr/include/libxml2 -I/usr/local/include/libxml2 -I/usr/local/include -I../../lib -I../.. -DNAME='"ser"' -DVERSION='"2.99.0-dev01-serk"' -DARCH='"i386"' -DOS='linux_' -DOS_QUOTED='"linux"' -DCOMPILER='"gcc 4.3.2"' -D__CPU_i386 -D__OS_linux -DSER_VER=2099000 -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_GETHOSTBYNAME2 -DHAVE_UNION_SEMUN -DHAVE_SCHED_YIELD -DHAVE_MSG_NOSIGNAL -DHAVE_MSGHDR_MSG_CONTROL -DHAVE_ALLOCA_H -DHAVE_TIMEGM -DHAVE_SCHED_SETSCHEDULER -DHAVE_EPOLL -DHAVE_SIGIO_RT -DSIGINFO64_WORKARROUND -DUSE_FUTEX -DHAVE_SELECT -DSER -DSER_MOD_INTERFACE -DMOD_NAME='"pa"' -c async_auth.c -o async_auth.o In file included from async_auth.c:1: pa_mod.h:54: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'pa_dbf' make[1]: *** [async_auth.o] Error 1 make[1]: Leaving directory `/home/darilion/software/siprouter/sip-router/modules_s/pa' make: *** [modules_s] Error 1
pa module includes srdb2 - shouldn't it include srdb1?
regards klaus
Klaus Darilion wrote:
make[1]: Entering directory `/home/darilion/software/siprouter/sip-router/modules_s/pa' gcc -fPIC -DPIC -g -O9 -funroll-loops -Wcast-align -minline-all-stringops -falign-loops -ftree-vectorize -mtune=athlon64 -Wall -I/usr/include/libxml2 -I/usr/local/include/libxml2 -I/usr/local/include -I../../lib -I../.. -DNAME='"ser"' -DVERSION='"2.99.0-dev01-serk"' -DARCH='"i386"' -DOS='linux_' -DOS_QUOTED='"linux"' -DCOMPILER='"gcc 4.3.2"' -D__CPU_i386 -D__OS_linux -DSER_VER=2099000 -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_GETHOSTBYNAME2 -DHAVE_UNION_SEMUN -DHAVE_SCHED_YIELD -DHAVE_MSG_NOSIGNAL -DHAVE_MSGHDR_MSG_CONTROL -DHAVE_ALLOCA_H -DHAVE_TIMEGM -DHAVE_SCHED_SETSCHEDULER -DHAVE_EPOLL -DHAVE_SIGIO_RT -DSIGINFO64_WORKARROUND -DUSE_FUTEX -DHAVE_SELECT -DSER -DSER_MOD_INTERFACE -DMOD_NAME='"pa"' -c async_auth.c -o async_auth.o In file included from async_auth.c:1: pa_mod.h:54: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'pa_dbf' make[1]: *** [async_auth.o] Error 1 make[1]: Leaving directory `/home/darilion/software/siprouter/sip-router/modules_s/pa' make: *** [modules_s] Error 1
pa module includes srdb2 - shouldn't it include srdb1?
I think there is similar problem in ser's rls module.
regards klaus
On 06/29/2009 11:27 PM, Klaus Darilion wrote:
pa module includes srdb2 - shouldn't it include srdb1?
srdb1 is Kamailio DB api and srdb2 is SER DB api.
Daniel
Daniel-Constantin Mierla wrote:
On 06/29/2009 11:27 PM, Klaus Darilion wrote:
pa module includes srdb2 - shouldn't it include srdb1?
srdb1 is Kamailio DB api and srdb2 is SER DB api.
strange, because some errors were gone when I changed to srdb1. Very strange.
thanks klaus
On Jun 30, 2009 at 09:18, Klaus Darilion klaus.mailinglists@pernau.at wrote:
Daniel-Constantin Mierla wrote:
On 06/29/2009 11:27 PM, Klaus Darilion wrote:
pa module includes srdb2 - shouldn't it include srdb1?
srdb1 is Kamailio DB api and srdb2 is SER DB api.
strange, because some errors were gone when I changed to srdb1. Very strange.
Well, some ser modules were never updated to the new ser db api (srdb2 in sip-router). They still use the old ser api. srdb1 is the kamilio api which is in fact ser/openser old api plus some updates and function prototype changes. srdb1 is very close to the original api and that's why you get closer to success when trying it. srdb2 is a complete rewrite and very different from the other apis.
Now some of the modules that do not compile might be removed anyway (e.g. I believe avpops functionality in ser is covered by the script avp support + the db_ops module and I don't think anybody did use that module for a very long time). For the others there are several options: 1. update them to srdb2 (the future) 2. update them to use srdb1 3. add srdb0, either as a lib or as a wrapper over srdb1 (I haven't looked at it, but it might be possible to do it only using some *.h wrappers).
(1) is definitely the most time consuming and it might not make sense for modules that use the db only in a "simple" way, so we might do either (2) or (3), whichever proves to be less work.
Andrei
On 30-06 10:45, Andrei Pelinescu-Onciul wrote:
On Jun 30, 2009 at 09:18, Klaus Darilion klaus.mailinglists@pernau.at wrote:
Daniel-Constantin Mierla wrote:
On 06/29/2009 11:27 PM, Klaus Darilion wrote:
pa module includes srdb2 - shouldn't it include srdb1?
srdb1 is Kamailio DB api and srdb2 is SER DB api.
strange, because some errors were gone when I changed to srdb1. Very strange.
Well, some ser modules were never updated to the new ser db api (srdb2 in sip-router). They still use the old ser api. srdb1 is the kamilio api which is in fact ser/openser old api plus some updates and function prototype changes. srdb1 is very close to the original api and that's why you get closer to success when trying it. srdb2 is a complete rewrite and very different from the other apis.
Now some of the modules that do not compile might be removed anyway (e.g. I believe avpops functionality in ser is covered by the script avp support + the db_ops module and I don't think anybody did use that module for a very long time). For the others there are several options:
- update them to srdb2 (the future)
- update them to use srdb1
This is what I have been thinking too, updating them to srdb1 is easy, compared to updating them to the new db api.
Jan.