Module: sip-router
Branch: janakj/oracle
Commit: f25b29befa559e3fb58c64a54fa43a550e269a3c
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=f25b29b…
Author: Jan Janak <jan(a)iptel.org>
Committer: Jan Janak <jan(a)iptel.org>
Date: Sun Feb 15 13:57:41 2009 +0100
Merge commit 'or/cvshead' into oracle
* commit 'or/cvshead':
Get rid of compilation warnings emitted by
- oracle module moved from experimental to the main tree
---
Module: sip-router
Branch: janakj/oracle
Commit: 9cdb3c3997c66e04a447bf6ba19d7d3ef7ff67e1
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=9cdb3c3…
Author: Jan Janak <jan(a)iptel.org>
Committer: Jan Janak <jan(a)iptel.org>
Date: Fri Feb 16 15:35:16 2007 +0000
- oracle module moved from experimental to the main tree
- libs and includes configured to match locations provided
by oracle-xe-client package (the original paths are commented)
- removed redefinition of ERR and DBG
- fixed tracker location in common.h
---
Module: sip-router
Branch: master
Commit: fa825fd0e8fa5c29ded4276a0e021df67a327897
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=fa825fd…
Author: Andrei Pelinescu-Onciul <andrei(a)iptel.org>
Committer: Andrei Pelinescu-Onciul <andrei(a)iptel.org>
Date: Fri Feb 13 17:28:40 2009 +0100
libsrdb1: futex warning fix
- added _BSD_SOURCE define if _XOPEN_SOURCE is manually defined
(the _XOPEN_SOURCE define in db_ut.h caused _BSD_SOURCE to be no
longer defined in features.h => _USE_MISC not defined =>
syscall() not declared in unistd.h.)
---
lib/srdb1/db_ut.h | 3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/lib/srdb1/db_ut.h b/lib/srdb1/db_ut.h
index 050a75b..9c936df 100644
--- a/lib/srdb1/db_ut.h
+++ b/lib/srdb1/db_ut.h
@@ -45,6 +45,9 @@
*/
#ifndef __OS_solaris
#define _XOPEN_SOURCE 600 /* glibc2 on linux, bsd */
+ #define _BSD_SOURCE 1 /* needed on linux to "fix" the effect
+ of the above define on
+ features.h/unistd.h syscall() */
#else
#define _XOPEN_SOURCE_EXTENDED 1 /* solaris */
#endif
This was me, there was a bug in the commit mail script which I hopefully
fixed.
I updated the master branch and added both versions of the database API. The
database library of SER 2.0 is in lib/srdb2, the database library of kamailio
is in lib/srdb1. There is the full history of the kamailio database library,
that's why there is so many commit messages in the previous email.
I had to do some changes in the database library taken from kamailio in order
to avoid conflicts between the two version, the changes are:
1) db_con_t has been renamed to db1_con_t
2) db_res_t has been renamed to db1_res_t
3) DB_INT, DB_STR,... macros have been renamed to DB1_INT, DB1_STR,...
4) The doxygen group db has been renamed to db1.
All the changes have been applied to the kamailio database library
synchronized yesterday, here is how you can get patches with the changes that
I did if you need them:
$ git-format-patch -o patches 18580
I also attached them to this email for your convenience, they should apply to
the current kamailio/db after stripping the path prefix off (patch option -p).
I will send a script to update other modules later tomorrow and also upload
the updated mysql driver which works with both versions of the database
library (i.e. that module should work with both ser and kamailio).
Jan.
On 12-02 23:25, sr-dev-owner(a)lists.sip-router.org wrote:
> As list administrator, your authorization is requested for the
> following mailing list posting:
>
> List: sr-dev(a)lists.sip-router.org
> From: new(a)sip-router.org
> Subject: text/plain; charset=UTF-8
> Reason: Post by non-member to a members-only list
>
> At your convenience, visit:
>
> http://lists.sip-router.org/cgi-bin/mailman/admindb/sr-dev
>
> to approve or deny the request.
> Date: Thu, 12 Feb 2009 23:25:34 +0100 (CET)
> From: New(a)sip-router.org, commits(a)sip-router.org, on(a)sip-router.org,
> branch(a)sip-router.org, master(a)sip-router.org
> Subject: text/plain; charset=UTF-8
> To: sr-dev(a)lists.sip-router.org
>
> From: sr-dev-request(a)lists.sip-router.org
> Subject: confirm af3499ce3479bf6be60ee69ed389474e0ddabf1c
>
> If you reply to this message, keeping the Subject: header intact,
> Mailman will discard the held message. Do this if the message is
> spam. If you reply to this message and include an Approved: header
> with the list password in it, the message will be approved for posting
> to the list. The Approved: header can also appear in the first line
> of the body of the reply.